[JIRA] (JENKINS-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title Mark Austin edited a comment on JENKINS-50886 Re: Declarative pipeline with pollSCM triggers 2 builds I'm seeing this happen with one of my teams using the multi-branch pipeline setup. Two different people are able to trigger the problem rather easily, but I can't for the life of me reproduce it, so this leads me to question if local browser configs/plugins are contributing to the problem. Now my use case is a little different since I don't even want polling, but I've noticed that PollSCM is switched on by default with any multibranch pipeline I setup. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190011.1524103101000.10762.1565280420252%40Atlassian.JIRA.
[JIRA] (JENKINS-50886) Declarative pipeline with pollSCM triggers 2 builds
Title: Message Title Mark Austin commented on JENKINS-50886 Re: Declarative pipeline with pollSCM triggers 2 builds I'm seeing this happen with one of my teams using the multi-branch pipeline setup. Two different people are able to trigger the problem rather easily, but I can't for the life of me reproduce it, so this leads me to question if local browser configs/plugins are contributing to the problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190011.1524103101000.10755.1565280360294%40Atlassian.JIRA.
[JIRA] (JENKINS-42852) JSONObject["administrativeMonitor"] is not a JSONArray.
Title: Message Title Mark Austin commented on JENKINS-42852 Re: JSONObject["administrativeMonitor"] is not a JSONArray. Oleg Nenashev ah okay. I didn't see anything for this specific case when I searched the DB, so I wanted to make sure ya'll were aware about it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42852) JSONObject["administrativeMonitor"] is not a JSONArray.
Title: Message Title
Mark Austin updated an issue
Jenkins / JENKINS-42852
JSONObject["administrativeMonitor"] is not a JSONArray.
Change By:
Mark Austin
Running on the latest versions of LTS and/or dev copy of Jenkins on a fresh install , I get the following stack trace when I try to disable the "Node marked offline due to health check" and/or "Too many scm polling threads" admin monitors: {code: java| title=Stack Trace|borderStyle=solid}javax.servlet.ServletException: net.sf.json.JSONException: JSONObject["administrativeMonitor"] is not a JSONArray. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at
[JIRA] (JENKINS-42852) JSONObject["administrativeMonitor"] is not a JSONArray.
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-42852 JSONObject["administrativeMonitor"] is not a JSONArray. Change By: Mark Austin Attachment: Screenshot_20170316_133145.png Attachment: Screenshot_20170316_133255.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42852) JSONObject["administrativeMonitor"] is not a JSONArray.
Title: Message Title Mark Austin created an issue Jenkins / JENKINS-42852 JSONObject["administrativeMonitor"] is not a JSONArray. Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Mar/16 5:31 PM Labels: jenkins Priority: Minor Reporter: Mark Austin Running on the latest versions of LTS and/or dev copy of Jenkins, I get the following stack trace when I try to disable the "Node marked offline due to health check" and/or "Too many scm polling threads" admin monitors: Stack Trace javax.servlet.ServletException: net.sf.json.JSONException: JSONObject["administrativeMonitor"] is not a JSONArray. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title
Mark Austin edited a comment on JENKINS-34876
Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Hey Scott,I guess we could just run a script like this as an alternative on the Jenkins master so that the main workspace has access to the properties file: {code} git ls-remote -t https://github.com/jenkinsci/github-plugin | awk '{print $2}' | cut -d '/' -f 3 | cut -d '^' -f 1 | sort -b -t . -k 1,1nr -k 2,2nr -k 3,3r -k 4,4r -k 5,5r | uniq | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > /tmp/versions.properties {code} That way we don't have to force Jenkins to double checkout the git repo per my older example.There are a number of ways you could do this. The end goal is to make sure that the script runs on a regular basis or immediately after the jenkins workspace has polled the git repo.For instance, you could have the script execute on the jenkins master directly through something as simple as a cron job.Or, you could also try running it with a post-merge git hook in the workspace, that way it runs each time after a "git pull" occurs. Here is a basic example that you could modify for your needs:https://gist.github.com/sindresorhus/7996717If you're familiar with incron (http://inotify.aiken.cz/?section=incron=why=en), you could have that daemon execute the script each time it notices a file change in the git checkout folder on the workspace or just wait for this bug to get patched. :-)Hope this helps...
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title
Mark Austin edited a comment on JENKINS-34876
Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Hey Scott, I guess we could just run a script like this as an alternative on the Jenkins master so that the main workspace has access to the properties file:git ls-remote -t https://github.com/jenkinsci/github-plugin | awk '{print $2}' | cut -d '/' -f 3 | cut -d '^' -f 1 | sort -b -t . -k 1,1nr -k 2,2nr -k 3,3r -k 4,4r -k 5,5r | uniq | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > /tmp/versions.propertiesThat way we don't have to force Jenkins to double checkout the git repo per my older example. There are a number of ways you could do this. The end goal is to make sure that the script runs on a regular basis or immediately after the jenkins workspace has polled the git repo.For instance, you could have the script execute on the jenkins master directly through something as simple as a cron job.Or, you could also try running it with a post-merge git hook in the workspace, that way it runs each time after a "git pull" occurs. Here is a basic example that you could modify for your needs:https://gist.github.com/sindresorhus/7996717If you're familiar with incron (http://inotify.aiken.cz/?section=incron=why=en), you could have that daemon execute the script each time it notices a file change in the git checkout folder on the workspace or just wait for this bug to get patched. :-)Hope this helps...
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Mark Austin edited a comment on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Hey Scott,There are a number of ways you could do this. The end goal is to make sure that the script runs on a regular basis or immediatley immediately after the slave builder jenkins workspace has polled the git repo.For instance, you could have the script execute on the slave jenkins master directly through something as simple as a cron job.Or, you could also try running it with a post-merge git hook in the workspace , that way it runs each time after a "git pull" occurs. Here is a basic example that you could modify for your needs:https://gist.github.com/sindresorhus/7996717If you're familiar with incron (http://inotify.aiken.cz/?section=incron=why=en), you could have that daemon execute the script each time it notices a file change in the git checkout folder on the slave workspace or just wait for this bug to get patched. :-)Hope this helps... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Mark Austin commented on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Hey Scott, There are a number of ways you could do this. The end goal is to make sure that the script runs on a regular basis or immediatley after the slave builder has polled the git repo. For instance, you could have the script execute on the slave directly through something as simple as a cron job. Or, you could also try running it with a post-merge git hook, that way it runs each time after a "git pull" occurs. Here is a basic example that you could modify for your needs: https://gist.github.com/sindresorhus/7996717 If you're familiar with incron (http://inotify.aiken.cz/?section=incron=why=en), you could have that daemon execute the script each time it notices a file change in the git checkout folder on the slave. ... or just wait for this bug to get patched. Hope this helps... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Mark Austin commented on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Hey Scott, Yes that is correct. I'd have the git repo poll and then ensure that the script is executed after each run. I know it's not ideal, but it works for now until Boguslaw Klimas get's things patched up. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Mark Austin edited a comment on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Hey Scott,Yes that is correct. I'd have the git repo poll and then ensure that the script is executed after each run. I know it's not ideal, but it works for now until [~klimas7] get's gets things patched up. :-) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Mark Austin edited a comment on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Hey Scott,Yes that is correct. I'd have the git repo poll and then ensure that the script is executed after each run poll . I know it's not ideal, but it works for now until [~klimas7] gets things patched up. :-) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Mark Austin commented on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM I observed the same behavior, but I came up with a hacky workaround... I wrote a shell script that will dump git tags into a sorted list that can be ingested as a property file when using the the Extended Choice Parameter plugin. 1) Run this script in the root of your git checkout dir: genVers.sh git tag -l --sort=version:refname | sort -r | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > /tmp/versions.properties 2) Install the Extended Choice Parameter plugin and add it to your job https://wiki.jenkins-ci.org/display/JENKINS/Extended+Choice+Parameter+plugin 3) Point the config to the property file you generated and set the key. See my attached example: 4) Test it Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Change By: Mark Austin Attachment: Screenshot_20160817_145625.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Change By: Mark Austin Attachment: Screenshot_20160817_145201.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Change By: Mark Austin Comment: I observed the same problem.I came up with a workaround, note that you need git 2.0 in order to do this...1) I wrote a script that is executed inside of the git checkout root:[code]git tag -l --sort=version:refname | sort -r | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > versions.properties[code] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Mark Austin commented on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM I observed the same problem. I came up with a workaround, note that you need git 2.0 in order to do this... 1) I wrote a script that is executed inside of the git checkout root: [code] git tag -l --sort=version:refname | sort -r | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > versions.properties [code] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25053) Record process ID of spawned process on Windows
Title: Message Title Mark Austin commented on JENKINS-25053 Re: Record process ID of spawned process on Windows With some modifications, perhaps using the process of capturing the PID from the attached bat script could help us track things better. AFAIK, the wmic command has been available for quite some time, should go as far back as windows xp and server 2003, so I doubt we'd cause noticeable breakage by calling out to this tool. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25053) Record process ID of spawned process on Windows
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-25053 Record process ID of spawned process on Windows Change By: Mark Austin Attachment: getPID.bat Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Change By: Mark Austin BlueOcean will not prompt for parameters when you schedule a pipeline build that requires them.!snapshot4.jpeg|thumbnail!The failed build also won't show up in the BlueOcean pipeline queue, but it will in the standard Jenkins UI.!snapshot5.jpeg|thumbnail!In my case, it fails since the withEnv wrapper will be null. Build 11 started working again because I removed the withEnv function from my pipeline test. However, entries seem to have a significant delay when loading in the BlueOcean UI. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Change By: Mark Austin BlueOcean will not prompt for parameters when you schedule a pipeline build that requires them. !snapshot4.jpeg|thumbnail! The failed build also won't show up in the BlueOcean pipeline queue, but it will in the standard Jenkins UI. !snapshot5.jpeg|thumbnail!!snapshot6.jpeg|thumbnail! In my case, it fails since the withEnv wrapper will be null. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Change By: Mark Austin BlueOcean will not prompt for parameters when you schedule a pipeline build that requires them.!snapshot4.jpeg|thumbnail!The failed build also won't show up in the BlueOcean pipeline queue, but it will in the standard Jenkins UI.!snapshot5.jpeg|thumbnail! !snapshot6.jpeg|thumbnail! In my case, it fails since the withEnv wrapper will be null. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Change By: Mark Austin Attachment: snapshot6.jpeg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Change By: Mark Austin Attachment: snapshot4.jpeg Attachment: snapshot5.jpeg Attachment: snapshot6.jpeg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin created an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Jul/21 7:18 PM Priority: Major Reporter: Mark Austin BlueOcean will not prompt for parameters when you schedule a pipeline build that requires them. The failed build also won't show up the BlueOcean queue, but it will in the standard Jenkins UI. In my case, it fails since the withEnv wrapper will be null. Add Comment
[JIRA] (JENKINS-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Change By: Mark Austin BlueOcean will not prompt for parameters when you schedule a pipeline build that requires them. The failed build also won't show up in the BlueOcean pipeline queue, but it will in the standard Jenkins UI. In my case, it fails since the withEnv wrapper will be null. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13153) "Upgrade Automatically" does not seem to work on Windows
Title: Message Title
Mark Austin edited a comment on JENKINS-13153
Re: "Upgrade Automatically" does not seem to work on Windows
Hey Daniel,I've managed to reproduce this issue multiple times using a full admin windows account while using the latest copy of winsw (1.18). It seems to me that the process that writes jenkins.war.tmp fails silently. I can confirm that the correct update is being downloaded, stored as jenkins.war.tmp and making a copy of the old file as jenkins.war.bak.!Screen Shot 2016-06-08 at 2.34.00 PM.png|thumbnail!I suspect it's happening due to the jenkins.exe still holding a file handle on the original war file and fails silently based off how I understand what's going on in the core code:https://github.com/jenkinsci/jenkins/blob/cf64ba04fe8b0312bb4492766d62b5a00b790432/core/src/main/java/hudson/lifecycle/Lifecycle.java#L137-L170It may be helpful to have the{code:java}canRewriteHudsonWar(){code}function report success vs failure in the logger. I guess it would be best to avoid throwing an exception to help prevent introducing API breakage.The windows event viewer will throw the following details when the service is terminated (that is , when you check the restart box), but even the OS logs fail to report a problem, so this fails silently by all accounts right now . No additional errors are reported in the wrapper log. Here is the windows event at the time the JVM is restarted after the update is downloaded to the system :{code}Log Name: ApplicationSource:JenkinsDate: 6/8/2016 2:12:14 PMEvent ID: 0Task Category: NoneLevel: InformationKeywords: ClassicUser: N/AComputer: reubenWinDescription:Child process [4860 - C:\jenkins\java\jre1.8.0_92\bin\java -server -d64 -Xrs -Xms2048m -Xmx2048m -XX:+AlwaysPreTouch -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djenkins.model.Jenkins.logStartupPerformance=true -Dhudson.udp=-1 -Dhudson.DNSMultiCast.disabled=true -jar "C:\jenkins\jenkins.war" --httpListenAddress=0.0.0.0 --httpsPort=-1 --httpPort=8080 --ajp13Port=-1 --webroot=C:\jenkins\webroot] terminated with -1073741510Event Xml: 0400x80
[JIRA] [core] (JENKINS-13153) "Upgrade Automatically" does not seem to work on Windows
Title: Message Title
Mark Austin edited a comment on JENKINS-13153
Re: "Upgrade Automatically" does not seem to work on Windows
Hey Daniel,I've managed to reproduce this issue multiple times using a full admin windows account while using the latest copy of winsw (1.18). It seems to me that the process that writes jenkins.war.tmp fails silently. I can confirm that the correct update is being downloaded, stored as jenkins.war.tmp and making a copy of the old file as jenkins.war.bak.!Screen Shot 2016-06-08 at 2.34.00 PM.png|thumbnail!I suspect it's happening due to the jenkins.exe still holding a file handle on the original war file and fails silently based off how I understand what's going on in the core code:https://github.com/jenkinsci/jenkins/blob/cf64ba04fe8b0312bb4492766d62b5a00b790432/core/src/main/java/hudson/lifecycle/Lifecycle.java#L137-L170It may be helpful to have the{code:java}canRewriteHudsonWar(){code}function report success vs failure in the logger. I guess it would be best to avoid throwing an exception to help prevent introducing API breakage.The windows event viewer will throw the following details when the service is terminated, but even the OS logs fail to report a problem right now , so this fails silently by all accounts right now:{code}Log Name: ApplicationSource:JenkinsDate: 6/8/2016 2:12:14 PMEvent ID: 0Task Category: NoneLevel: InformationKeywords: ClassicUser: N/AComputer: reubenWinDescription:Child process [4860 - C:\jenkins\java\jre1.8.0_92\bin\java -server -d64 -Xrs -Xms2048m -Xmx2048m -XX:+AlwaysPreTouch -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djenkins.model.Jenkins.logStartupPerformance=true -Dhudson.udp=-1 -Dhudson.DNSMultiCast.disabled=true -jar "C:\jenkins\jenkins.war" --httpListenAddress=0.0.0.0 --httpsPort=-1 --httpPort=8080 --ajp13Port=-1 --webroot=C:\jenkins\webroot] terminated with -1073741510Event Xml: 0400x80
[JIRA] [core] (JENKINS-13153) "Upgrade Automatically" does not seem to work on Windows
Title: Message Title
Mark Austin edited a comment on JENKINS-13153
Re: "Upgrade Automatically" does not seem to work on Windows
Hey Daniel,I've managed to reproduce this issue multiple times using a full admin windows account while using the latest copy of winsw (1.18). It seems to me that the process that writes jenkins.war.tmp fails silently. I can confirm that the correct update is being downloaded, stored as jenkins.war.tmp and making a copy of the old file as jenkins.war.bak.!Screen Shot 2016-06-08 at 2.34.00 PM.png|thumbnail!I suspect it's happening due to the jenkins.exe still holding a file handle on the original war file and fails silently based off how I understand what's going on in the core code:https://github.com/jenkinsci/jenkins/blob/cf64ba04fe8b0312bb4492766d62b5a00b790432/core/src/main/java/hudson/lifecycle/Lifecycle.java#L137-L170It may be helpful to have the{code:java}canRewriteHudsonWar(){code}function report success vs failure in the logger. I guess it would be best to avoid throwing an exception to help prevent introducing API breakage.The windows event viewer will throw the following details when the service is terminated, but even the OS logs fail to report a problem right now, so this fails silently by all accounts right now:{code}Log Name: ApplicationSource:JenkinsDate: 6/8/2016 2:12:14 PMEvent ID: 0Task Category: NoneLevel: InformationKeywords: ClassicUser: N/AComputer: reubenWinDescription:Child process [4860 - C:\jenkins\java\jre1.8.0_92\bin\java -server -d64 -Xrs -Xms2048m -Xmx2048m -XX:+AlwaysPreTouch -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djenkins.model.Jenkins.logStartupPerformance=true -Dhudson.udp=-1 -Dhudson.DNSMultiCast.disabled=true -jar "C:\jenkins\jenkins.war" --httpListenAddress=0.0.0.0 --httpsPort=-1 --httpPort=8080 --ajp13Port=-1 --webroot=C:\jenkins\webroot] terminated with -1073741510Event Xml: 0400x80
[JIRA] [core] (JENKINS-13153) "Upgrade Automatically" does not seem to work on Windows
Title: Message Title Mark Austin commented on JENKINS-13153 Re: "Upgrade Automatically" does not seem to work on Windows Hey Daniel, I've managed to reproduce this issue multiple times using a full admin windows account while using the latest copy of winsw (1.18). It seems to me that the process that writes jenkins.war.tmp fails silently. I can confirm that the correct update is being downloaded, stored as jenkins.war.tmp and making a copy of the old file as jenkins.war.bak. I suspect it's happening due to the jenkins.exe still holding a file handle on the original war file and fails silently based off how I understand what's going on in the core code: https://github.com/jenkinsci/jenkins/blob/cf64ba04fe8b0312bb4492766d62b5a00b790432/core/src/main/java/hudson/lifecycle/Lifecycle.java#L137-L170 It may be helpful to have the canRewriteHudsonWar() function report success vs failure in the logger. I guess it would be best to avoid throwing an exception to help prevent introducing API breakage. The windows event viewer will throw the following details when the service is terminated, but even the OS logs fail to report a problem right now, so this fails silently by all accounts right now: Log Name: Application Source:Jenkins Date: 6/8/2016 2:12:14 PM Event ID: 0 Task Category: None Level: Information Keywords: Classic User: N/A Computer: reubenWin Description: Child process [4860 - C:\jenkins\java\jre1.8.0_92\bin\java -server -d64 -Xrs -Xms2048m -Xmx2048m -XX:+AlwaysPreTouch -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djenkins.model.Jenkins.logStartupPerformance=true -Dhudson.udp=-1 -Dhudson.DNSMultiCast.disabled=true -jar "C:\jenkins\jenkins.war" --httpListenAddress=0.0.0.0 --httpsPort=-1 --httpPort=8080 --ajp13Port=-1 --webroot=C:\jenkins\webroot] terminated with -1073741510 Event Xml: "http://schemas.microsoft.com/win/2004/08/events/event">"Jenkins" /> "0">0 4 0 0x80 "2016-06-08T18:12:14.0Z" /> 1159 Application reubenWin System> Child process [4860 - C:\jenkins\java\jre1.8.0_92\bin\java -server -d64 -Xrs -Xms2048m -Xmx2048m -XX:+AlwaysPreTouch -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djenkins.model.Jenkins.logStartupPerformance=true -Dhudson.udp=-1 -Dhudson.DNSMultiCast.disabled=true -jar "C:\jenkins\jenkins.war" --httpListenAddress=0.0.0.0 --httpsPort=-1 --httpPort=8080 --ajp13Port=-1 --webroot=C:\jenkins\webroot] terminated with -1073741510 I've attached a copy of my jenkins.xml file if that helps: jenkins.xml Note that I intentionally use custom folder paths to help precent windows from locking up files in use, hence the seperation of individual directories like:
[JIRA] [core] (JENKINS-13153) "Upgrade Automatically" does not seem to work on Windows
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-13153 "Upgrade Automatically" does not seem to work on Windows Change By: Mark Austin Attachment: Screen Shot 2016-06-08 at 2.34.00 PM.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13153) "Upgrade Automatically" does not seem to work on Windows
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-13153 "Upgrade Automatically" does not seem to work on Windows Change By: Mark Austin Attachment: jenkins.xml Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-34722) Unbounded searches with BuildUtil.getDownstreamBuild
Title: Message Title
Mark Austin updated an issue
Jenkins / JENKINS-34722
Unbounded searches with BuildUtil.getDownstreamBuild
Change By:
Mark Austin
BuildUtil.getDownstreamBuild does an unbounded search of build records, which is never acceptable due to Jenkins lazy-loading, and particular not in the context of an HTTP handler thread.It would be better is to use AbstractBuild.getDownstreamBuilds(AbstractProject), which is efficient, though it only works for project chains which are correctly configured with fingerprints. Example:{code}"Handling GET /jenkins/org/job/Pipelines/job/org-build/view/Pipelines_View/ from 10.x.x.x : RequestHandlerThread[#2296] View/index.jelly" Id=126293 BLOCKED on hudson.model.RunMap@607d5beb owned by "Handling GET /jenkins/org/job/Pipelines/job/org-build/ from 10.x.x.x : RequestHandlerThread[#2297] View/index.jelly" Id=126471at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java)- blocked on hudson.model.RunMap@607d5bebat jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:448)at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:356)at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:332)at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:74)at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:63)at java.util.AbstractMap$2$1.next(AbstractMap.java:396)at au.com.centrumsystems.hudson.plugin.util.BuildUtil.getDownstreamBuild(BuildUtil.java:66){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [build-pipeline-plugin] (JENKINS-34722) Unbounded searches with BuildUtil.getDownstreamBuild
Title: Message Title Mark Austin created an issue Jenkins / JENKINS-34722 Unbounded searches with BuildUtil.getDownstreamBuild Issue Type: Improvement Assignee: Unassigned Components: build-pipeline-plugin Created: 2016/May/11 3:29 AM Priority: Major Reporter: Mark Austin BuildUtil.getDownstreamBuild does an unbounded search of build records, which is never acceptable due to Jenkins lazy-loading, and particular not in the context of an HTTP handler thread. It would be better is to use AbstractBuild.getDownstreamBuilds(AbstractProject), which is efficient, though it only works for project chains which are correctly configured with fingerprints. Add Comment
[JIRA] [core] (JENKINS-32443) java.nio.file.AccessDeniedException on windows master
Title: Message Title Mark Austin created an issue Jenkins / JENKINS-32443 java.nio.file.AccessDeniedException on windows master Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Jan/16 10:47 PM Environment: Jenkins 1.609.15.1 Windows Server 2012 R2 Oracle JDK 1.8.0_65 Priority: Trivial Reporter: Mark Austin Running a build from windows will end successfully, however it will throw the following AccessDeniedException. Started by user u...@host.com ln \\domain\public\projects\eng\test\project\master\task\lastSuccessfulBuild C:\jenkins\data\jobs\eng\jobs\test\jobs\project\jobs\master\jobs\task\lastSuccessful failed java.nio.file.AccessDeniedException: C:\jenkins\data\jobs\eng\jobs\test\jobs\project\jobs\master\jobs\task\lastSuccessful at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.createSymbolicLink(Unknown Source) at java.nio.file.Files.createSymbolicLink(Unknown Source) at sun.reflect.GeneratedMethodAccessor357.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at
[JIRA] [core] (JENKINS-32443) java.nio.file.AccessDeniedException on windows master
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-32443 java.nio.file.AccessDeniedException on windows master Change By: Mark Austin Environment: Jenkins 1.609.15.1Windows Server 2012 R2Oracle JDK 1.8. 0_65 0_66 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31344) Allow users to clear out individual approved signatures from the UI
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-31344 Allow users to clear out individual approved signatures from the UI Change By: Mark Austin Larger installations may have a lot of approved signatures and the current UI only allows one to clear all signatures with a "Clear Approvals" button (see screen shot below). It would be nice if the UI would allow one to clear individual signatures. A base example would be if the user accidentally approved System.exit but does not want that to run!This seems like a matter of reversing the way things are hashed in the below code and adding it as a new function that is called by a button from the UI?https://github.com/jenkinsci/script-security-plugin/blob/master/src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/ScriptApproval.java #L142 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31344) Allow users to clear out individual approved signatures from the UI
Title: Message Title Mark Austin created an issue Jenkins / JENKINS-31344 Allow users to clear out individual approved signatures from the UI Issue Type: Improvement Assignee: Jesse Glick Attachments: Unapprove.PNG Components: workflow-plugin Created: 02/Nov/15 2:55 PM Environment: workflow-1.10.1 FreeBSD 10.2 Jenkins 1.635 OpenJDK 1.8.0_60-b24 Priority: Minor Reporter: Mark Austin Larger installations may have a lot of approved signatures and the current UI only allows one to clear all signatures "Clear Approvals" (see screen shot below). It would be nice if the UI would allow one to clear individual signatures. A base example would be if the user accidentally approved System.exit but does not want that to run! This seems like a matter of reversing the way things are hashed in the below code and adding it as a new function that is called by a button from the UI?
[JIRA] [maven-plugin] (JENKINS-31322) Parallel maven jobs run out of order
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-31322 Parallel maven jobs run out of order How the UI displays the info. Change By: Mark Austin Attachment: build_order3.JPG Attachment: build_order2.JPG Attachment: build_order.JPG Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-31322) Parallel maven jobs run out of order
Title: Message Title Mark Austin created an issue Jenkins / JENKINS-31322 Parallel maven jobs run out of order Issue Type: Bug Assignee: Unassigned Attachments: config.xml, maven_log.log Components: maven-plugin Created: 30/Oct/15 9:47 PM Environment: Jenkins 1.635 FreeBSD 10.1 OpenJDK 1.8.0_60 Google Chrome 46.0.2490.80 maven-plugin 2.12.1 Labels: plugin maven Priority: Major Reporter: Mark Austin Steps to reproduce: 1) Create a new maven project and make sure it is configured to run in parallel (use my provided config.xml for reference). 2) Execute 4 builds at the same time and wait for them to complete 3) Run another build after the 4th
[JIRA] [maven-plugin] (JENKINS-31322) Parallel maven jobs run out of order
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-31322 Parallel maven jobs run out of order Change By: Mark Austin Environment: Jenkins 1.635FreeBSD 10. 1 2 OpenJDK 1.8.0_60Google Chrome 46.0.2490.80maven-plugin 2.12.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31190) Running batch scripts killed after Jenkins restart
Title: Message Title Mark Austin created an issue Jenkins / JENKINS-31190 Running batch scripts killed after Jenkins restart Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 27/Oct/15 2:48 PM Environment: Windows Priority: Minor Reporter: Mark Austin The following error occurs while running bat scripts from workflow in a windows environment. Running: Allocate node : Start Running on SIOBOS357 in E:\workspace\slave_test\Jenkins\workspace\BAUHAUS_TEST Running: Allocate node : Body : Start … [exec] "E:/Workspace/slave_test/Jenkins/workspace/BAUHAUS_TEST/Load4W/_gen/swb/filegroup/includes/project/Rte_ComM_Type.h", line 48 (col. 80): warning #1-D: last line of file ends without a newline Terminate batch job (Y/N)? … Running: Allocate node : Body : End Running: Allocate node : End Running: End of Workflow ERROR: script returned exit code 130 Finished: FAILURE Something killed the batch script running ant, and Jenkins noted the erroneous exit status. There is no record of what killed it or why.
[JIRA] [workflow-plugin] (JENKINS-30641) Limit workflow to SCM checkout only
Title: Message Title Mark Austin created an issue Jenkins / JENKINS-30641 Limit workflow to SCM checkout only Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 24/Sep/15 9:19 PM Environment: Any Labels: jenkins configuration plugin scm plugins workflow Priority: Minor Reporter: Mark Austin It would be nice to add an option in Jenkins to enforce users to only be allowed to run workflow groovy code from a file based out of SCM and disallow the use of inline embedded groovy code. Perhaps this could be an option that is switched on from "Configure Jenkins".
[JIRA] [workflow-plugin] (JENKINS-30641) Limit workflow to SCM checkout only
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-30641 Limit workflow to SCM checkout only Change By: Mark Austin Labels: configuration jenkins plugin plugins scm workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-30230) URL rendering error with folder list views
Title: Message Title Mark Austin created an issue Jenkins / JENKINS-30230 URL rendering error with folder list views Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2015-08-31 at 2.53.08 PM.png Components: multijob-plugin Created: 31/Aug/15 9:57 PM Priority: Major Reporter: Mark Austin Tested on 1.16... 1. Create a multi-job build in a list view 2. Create a job in a folder and set it as one of the phases of the multi-job build and save 3. Now when viewing the multi-job page, if you click on the reference to the job in the folder, the URL points to a non-existent page Notice that the job folder is being completely ignored. Add Comment
[JIRA] [multijob-plugin] (JENKINS-30230) URL rendering error with folder list views
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-30230 URL rendering error with folder list views Change By: Mark Austin Attachment: Screen Shot 2015-08-31 at 2.37.44 PM.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
