I was told that a job cannot config the email notification, jenkins says 500 internal server error.
I found out that the problem was about the email-ext plugin. The default Mailer worked fine. Any job using the email-ext plugin cannot save configuration, even no change of the configuration.
I could not find what happens, the jenkins log didn't say anything.
I update the jenkins(2.72, then 2.73), and update all the plugins. problem did not disappear.
I uninstalled the plugin email-ext and tried to reinstall, but then jenkins said 500, so I manually remove the plugin/email-ext/ and the ...email-ext-config.xml, then restart the jenkins.
now any operation with any plugin will return 500 internal server error, even config the job with default mailer.
how could I fix this?
Related
In jenkins I am not able to add plugins,when I search for plugins I am getting a message as in the picture.
It looks like you have installed a plugin, but have yet to restart your Jenkins instance. If Jenkins is running as a service, simply stop and start the service command line, or check the checkbox in your screenshot above to restart Jenkins when no jobs are running and refresh the browser.
Should do the trick.
I can no longer add an email-ext post build step to my jenkins jobs.
This worked before, but the I upgraded to jenkins 2.7.1 and the email-ext plugin 2.44.
Now, when I add an post build step to a job and try to save the modified job, I will be taken to a login page and this page will lead to an error and the new step will not be saved.
Frank
One solution is to downgrade your jenkins to earlier working version.
Try uninstall/reinstall of email plugin.
If you are OK with the New version and not willing to downgrade and wanted email as a post build step, follow the below steps.
Steps:
Login to the server where you have installed jenkins and traverse to the that jobs config.xml path.
add the email section to the job's config.xml [You can refer to other existing job's config.xml which contains email section as a post build and use the same in this job, paste those lines in your job's config.xml]
Save you changes.
Now come back to your jenkins GUI and goto manage jenkins section.
Click on "Reload Configuration from Disk", This will reload your changes from server.
You will now be able to find the changes saved.
Another way is to update the job config.xml from jenkins command line.
search for jenkins-cli.jar and you will find a route.
Okay so I'm using Openshift to host my projects, and I just made a new account there yesterday. Yesterday I also used the command yo angular-fullstack:openshift in my `git-bash´ console to make an application there and to push my project to it. Worked fine.
Then I deleted the application on Openshift and today I want to upload it again. I run the same procedure and the same command. However now I get an error telling me that the hostname doesn't exist. Is this something which I can fix or is it one of those "try again later" problems?
The Error
Uploading your initial application code.
This may take several minutes depending on your connection speed...
× ssh: Could not resolve hostname unityacademy-academiaunitate.rhcloud.com: no address associated with name
× fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Delete your 'dist' folder and redo a grunt build to generate a new 'dist' folder. This will ensure that your 'dist' folder is clean and not interfering with the creation process of you app. Make sure the old app on OpenShift is deleted and do the yo angular-fullstack:openshift command again.
This should do the trick.
I cannot get my server code to update. I'm running a PHP instance on GAE and no matter what I do, the files won't update. In the source code view, I can see the files have updated, but when I attempt to access the updated file, I'm still viewing the old version. I've also attempted disconnecting my Bitbucket repo and using the appcfg.py update project-name command, but the files aren't refreshing when I attempt to access them. I'm not sure what to do to force the changes to take place.
My app.yaml contains the following code
- url: /(.+\.php)$
script: \1
secure: always
So the files should be getting read, right?
I was able to figure out what went wrong. I downloaded my code using appcfg.py download_app -A <your_app_id> -V <your_app_version> <output-dir> and noticed that I was downloading the old versions of the files (and wasn't downloading the new files). Turns out using source control within GAE will upload new code, but won't deploy it. I attempted to use appcfg.py update project-name one more time, but it didn't work. Turns out I didn't disconnect my Bitbucket account (could have sworn that I did...). Once disconnected, I was able to update the project using appcfg.py update project-name. While I was figuring this out, I reached out to Google support and received this message:
To use the feature of push to deploy you need to spin-up the Jenkins
Instance on GCE (Google Compute Engine) and then it will take the
updated code and execute it in the environment. Go through [1] for how
to enable the Jenkins instance and its configuration according to
different run time.
In your issue, you just mirrored the code from Bit Bucket to Cloud
Repository, as it is just doing the version control for the
application not executing the application. So basically you have have
the option of using Jenkins instance as I described above to test the
different version of the code or using the appcfg.py update command
from your local repository.
I haven't attempted to install and use Jenkins since I fixed it after disconnecting my Bitbucket account), but it may help others who have run into this problem.
I don't know why, but when I launch my application I suddenly always receive the following error (that before never appeared):
java.lang.NoSuchMethodError: com.google.gdata.client.authn.oauth.GoogleOAuthParameters.setOAuthType(Lcom/google/gdata/client/authn/oauth/OAuthParameters$OAuthType;)
The line of code generating the error is:
oauthParameters.setOAuthType(OAuthParameters.OAuthType.TWO_LEGGED_OAUTH);
That error wasn't appeared before, always in eclipse there wasn't an error and all was working fine.
I've never changed library. It seems that when I deploy to app-engine it doesn't upload the jar with that class?
Since you're only seeing this issue when you deploy, it sounds like you've included the gdata-java-client jars in a location so that they are visible to your local Java runtime, but are not sent to the App Engine server upon deployment.
The easiest way to resolve this is to include the gdata-java-client and its dependencies in the war/WEB-INF/lib directory of your application, and to reference those jars in your Java build path within Eclipse.