I installed the NodeLabelParameter Plugin to allow me to set a node to use for a build, but when selecting Node or Label parameter types the parameter box isn't appended to the list of parameters. I can see the render request in network tab with the expected html. No errors in console.
I have tried uninstalling and reinstalling the Plugin, removed other Plugins to see if there was any conflicts but nothing seems to work.
Has anyone ever had this issue before and might be able to advise?
I am running Jenkins 1.264.3 and NodeLabelParameter (1.7.2)
After some serious debugging, I found the last script to run before Jenkins getting the render file was Adguard. This seemed to have been the issue, disabled Adguard and next click of adding the parameter it appeared.
Related
I am looking for some kind of plugin or some kind of workaround by which i can have a button to rerun a build with same parameters on console page . so we can directly click and a new build will run without passing new params.
I tried some searches but not able to find this kind of plugin.
This is what i found which is helping me.
https://wiki.jenkins.io/display/JENKINS/Rebuild+Plugin
Jenkins 1.573 / 1.628 or latest version.
Build Pipeline plugin : 1.4.8 (latest)
Till last week everything was OK, today I'm seeing that when I click on the first job in the Build Pipeline dashboard view (to run a process), it used to prompt parameters but not anymore. It's giving me a BLANK white modal window / popup page and there are no input parameters visible.
Any idea! what I may be missing.
http://s000.tinyupload.com/download.php?file_id=03793493629898722609&t=0379349362989872260930671
I had a similar issue, but solution was different. In my Jenkins configuration, the Jenkins URL was not set correctly - it was a http address, whereas my Jenkins was set up with TLS. So make sure that Manage Jenkins - Configure System - Jenkins URL is set correctly.
Finally found the issue.
The issue is either with the Build Pipeline plugin (not using / compatible with Chrome browser) OR it's a Chrome browser issue.
I somehow had Chrome session opened the other day and when I click on "Run" (top section) to start the pipeline / job run, it shows me a BLANK modal window and doesn't show me any parameters.
Version 46.0.2490.86 m
Google Chrome is up to date.
While the same is working in IE or Firefox (I have the latest versions). I guess, I'll use FF/IE for now.
I'm trying to configure some features in Jenkins for our project.
In the process of configuring Editable Email Notification, I have created a new jelly script file in $JENKINS_HOME/email-templates folder as shown here
and accessing it in Jenkins config like this
When I build the job, with these setting, I'm getting email with the content
"JellyException: Could not parse Jelly script : null"
Thanks in advance!!
I faced a similar issue after I updated my Jenkins installation. I used the "Email Template Testing" feature to verify my script, but kept getting
JellyException: Could not parse Jelly script : null
In my case the issue was caused because of the use of jelly:util library in my jelly script. The script used u:loadText and u:file tags.
It seems that newer version of Jenkins do not include the jelly:util library, required for using the util tags. I resolved the issue by manually placing the commons-jelly-tags-util-1.1.1.jar file in the \war\WEB-INF\lib directory of Jenkins and restarting it.
There are two issues that are usually encountered when working with email templates (and there is another issue#2.5 will i'll explain as well :) )
I faced this issue when I copied/created new scripts from a different user rather than the one that Jenkins uses to run as. So in this case if 'ubuntu' is not the user that runs Jenkins as well, consider chowning the file and group to the user/group of jenkins user.
There were times when my jelly actually had an error which could not let it be parsed. I came to know about it from using the 'Email Template Testing' option available in the job options, which resulted in the same error
Now for the 2.5 issue
2.5. Please be cognizant of the fact that jelly templates have a different placeholder than the template-email-templates.
The '.template' files are loaded using ${SCRIPT} and '.jelly' Jelly scripts are loaded using ${JELLY_SCRIPT} tags, if you use JELLY_SCRIPT tag to load a template, you might end up with the same error as well.
This point is naive but it's worth listing it here so that anyone with this issue has all the checkpoints required to fix this issue.
I was able to create the new job but I am NOT able to add any build step.
This behaviour is reproducible and it occurs when I try to do it from the initial “configure” page I get after job creation as well as with a later configure attempt. And its persists for all job types.
It does not depend on whether I am logged in or not.
The problem is that when I open the “add build step” I get a selection of possible job types (“shell script”, “windows batch”, …) but when I select one of those nothing more happens.
I also have other jobs of this type already up and running and I am also not able to add more build steps to those.
I had this with v1.625.3, all of a sudden. Problem in Chrome and FF. Workaround was to use IE.
I am not able to display the jenkins homepage properly.
I have installed two VM with jenkins server and accessing the jenkins through putty and windows browser. Scenarion of two jenkins are
with normal connection [working]
in vpn connection [not working]
i can view the homepage of 1st, but not getting proper view of 2nd machine.
It displays only text not working. I mean only texts of login ,logout and build now etc.
when i click on this text getting following error
"Not Found
The requested URL /login was not found on this server."
There is no browser issues i have tried it 2-3 browsers.
I think this is jenkins issues or something else plz help.
You share so few details about how you installed Jenkins and what is the environment that you should not expect any good answers. I suspect the problem is around the correct use of the Jenkins --prefix command line parameter. It changes the way Jenkins constructs URLs for links. I hope this helps. If not, you should consider telling us more about your setup.