[JIRA] (JENKINS-42520) Header content wraps
Title: Message Title Josh McDonald stopped work on JENKINS-42520 Change By: Josh McDonald Status: In Progress Open 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-42520) Header content wraps
Title: Message Title Josh McDonald resolved as Fixed Jenkins / JENKINS-42520 Header content wraps Change By: Josh McDonald Status: Open Resolved Resolution: Fixed 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Daniel Wilmer commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Ok, this issue is not triggerd by a Jenkins update. I have updated jenkins today via apt-get update ; apt-get upgrade and the Pipelines are still awaiting and accepting user input. Maybe it has to do with plugin updates? 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-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Michael Neale edited a comment on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders ok put it here for now: [https://wiki.jenkins-ci.org/display/JENKINS/Blue+Ocean+Plugin][~jamesdumay] what do you think about the 404 page linking to some config doco at some point? The encoding of slashes is causing some major grief. 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-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Michael Neale commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders ok put it here for now: https://wiki.jenkins-ci.org/display/JENKINS/Blue+Ocean+Plugin James Dumay what do you think about the 404 page linking to some config doco at some point? 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-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Blue Ocean only for us as well. I never even saw a 404 page. In my case I just got a white screen of loneliness. The readme seems like a good place. 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-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Michael Neale commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Kevin Burnett it is such a beautiful page - hard to cry so much over it. That is not a bad idea. I'll add it to wiki right away, but then consider adding a link to that on the 404 page 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-40143) Duplicate email with Extended E-mail Notification
Title: Message Title Helene W commented on JENKINS-40143 Re: Duplicate email with Extended E-mail Notification Yes, they were configured the same way. In the job xml the post build action with the email stuff is exactly the same. Even when I delete the post build action from the (old) job, save it an add it again, emails are sent double. 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-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Kevin Burnett commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders We only had issues with links to blue ocean pages. I can suggest the blue ocean 404 page as a possible place to put a link to the docs. I found myself on that page, weeping softly, many times. 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-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Michael Neale commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Justin Rainwater There certainly is - lots of places. But which one? Jenkins.io website under /doc? blueocean README, blueocean wiki? Justin Rainwater Kevin Burnett does this apply to classic URIs or just to blue ocean (this will inform where to put the content/tips). 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-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Yes thank you Kevin Burnett! I forwarded this info to our Jenkins admins. Turns out we use tomcat instead but they found the tomcat version of those commands as follows: -Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true -Dorg.apache.catalina.connector.CoyoteAdapter.ALLOW_BACKSLASH=true Michael Neale is there somewhere this could be documented in case others run into it? This is a huge breakthrough for us. Now after months we can finally start playing with blue ocean! 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-39997) Bitbucket Build Status Notifier Plugin not reporting build status when job is in folder
Title: Message Title Sud Ramasamy updated an issue Jenkins / JENKINS-39997 Bitbucket Build Status Notifier Plugin not reporting build status when job is in folder Change By: Sud Ramasamy Comment: I'm seeing the same issue with a Maven style project both at the root level and also when nested inside a Folder in Jenkins. 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-39997) Bitbucket Build Status Notifier Plugin not reporting build status when job is in folder
Title: Message Title Sud Ramasamy edited a comment on JENKINS-39997 Re: Bitbucket Build Status Notifier Plugin not reporting build status when job is in folder I'm seeing the same issue with a Maven style project both at the root level and also when nested inside a Folder in Jenkins. 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-39997) Bitbucket Build Status Notifier Plugin not reporting build status when job is in folder
Title: Message Title Sud Ramasamy commented on JENKINS-39997 Re: Bitbucket Build Status Notifier Plugin not reporting build status when job is in folder I'm seeing the same issue with a Maven style project nested inside a Folder in Jenkins. 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-38046) Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline
Title: Message Title
Austin Phillips edited a comment on JENKINS-38046
Re: Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline
Here's another workaround using a normal pipeline job with the gerrit trigger plugin. * Set up Gerrit triggers as per normal * Set up Pipeline with 'Pipeline script from SCM', using the Gerrit environment variables as source information for the Jenkinsfile * Use a Jenkinsfile in your source as normal, complete with 'checkout scm' step.Configuration of the Pipeline SCM is as follows: * Set 'Repository URL' to {{$GERRIT_SCHEME://$GERRIT_HOST:$GERRIT_PORT/$GERRIT_PROJECT}} * Click the 'Advanced' button and set 'Refspec' to {{$GERRIT_REFSPEC:$GERRIT_REFSPEC}} * Set 'Branches to build' to {{$GERRIT_REFSPEC}} * If desired, add 'Advanced clone behaviours' with 'Shallow clone' enabled with a 'Shallow clone depth' set to 1. * Untick 'Lightweight checkout' Then, in your Gerrit repository Jenkins file: {noformat} node { stage('Checkout') { checkout scm } stage('Build') { echo "Building...' }}{noformat} Additional information: * The advantage of this method is that there is only a single Jenkinsfile specification which lives in your SCM. * The Pipeline configuration can be consistent across multiple projects as all of the SCM information is derived from Gerrit Trigger environment variables. The Gerrit Trigger parameters become the source for the Jenkinsfile pipeline definition. * The Jenkins master will check out a copy of the repository on the master to get access to the Jenkinsfile (ie Not in a workspace) * The 'checkout scm' step inside the pipeline will check out the code according to the SCM information entered in the pipeline step. Because the checkout occurs inside a 'node' block, the source repo ends up being checked out twice. Once to obtain the Jenkinsfile by the master, once as part of the Jenkinsfile pipeline step. The shallow clone options may help speed things up here. * This has only been tested with the 'Patchset Created' Gerrit Trigger type. * The 'Lightweight checkout' options appears not to work due to the way that git is used for this option. Following error is generated: hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/$GERRIT_REFSPEC:refs/remotes/origin/$GERRIT_REFSPEC --prune" returned status code 128:
Add Comment
[JIRA] (JENKINS-38046) Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline
Title: Message Title
Austin Phillips commented on JENKINS-38046
Re: Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline
Here's another workaround using a normal pipeline job with the gerrit trigger plugin.
Set up Gerrit triggers as per normal
Set up Pipeline with 'Pipeline script from SCM', using the Gerrit environment variables as source information for the Jenkinsfile
Use a Jenkinsfile in your source as normal, complete with 'checkout scm' step.
Configuration of the Pipeline SCM is as follows:
Set 'Repository URL' to $GERRIT_SCHEME://$GERRIT_HOST:$GERRIT_PORT/$GERRIT_PROJECT
Click the 'Advanced' button and set 'Refspec' to $GERRIT_REFSPEC:$GERRIT_REFSPEC
Set 'Branches to build' to $GERRIT_REFSPEC
If desired, add 'Advanced clone behaviours' with 'Shallow clone' enabled with a 'Shallow clone depth' set to 1.
Then, in your Gerrit repository Jenkins file:
node {
stage('Checkout') {
checkout scm
}
stage('Build') {
echo "Building...'
}
}
Additional information:
The advantage of this method is that there is only a single Jenkinsfile specification which lives in your SCM.
The Pipeline configuration can be consistent across multiple projects as all of the SCM information is derived from Gerrit Trigger environment variables. The Gerrit Trigger parameters become the source for the Jenkinsfile pipeline definition.
The Jenkins master will check out a copy of the repository on the master to get access to the Jenkinsfile (ie Not in a workspace)
The 'checkout scm' step inside the pipeline will check out the code according to the SCM information entered in the pipeline step. Because the checkout occurs inside a 'node' block, the source repo ends up being checked out twice. Once to obtain the Jenkinsfile by the master, once as part of the Jenkinsfile pipeline step. The shallow clone options may help speed things up here.
This has only been tested with the 'Patchset Created' Gerrit Trigger type.
[JIRA] (JENKINS-40477) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild
Title: Message Title
Zee Maqbool commented on JENKINS-40477
Re: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild
Is there anyway to get NodeName for pipeline jobs in common-library functions ? e.g. something like def mJenJobs = jenkins.model.Jenkins.getActiveInstance()..getAllItems() def mJenJobsSize = mJenJobs.size() def mResult = [] as Set for (i = 0; i < mJenJobsSize; i++) { def locJob = mJenJobs[i] def running = locJob.getLastBuild().isBuilding() if (running) { def build = locJob.getLastBuild() println "[Node " + locJob.getLastBuiltOn().getDisplayName()+ "] " // Option 1 println "[Node " + build.getExecutor().getOwner().getName()+ "] " // Option 2 } } I have tried both options in latest Jenkins (2.48) for a MultiBranchPipeline job but I get empty strings for Node value, is there any way I can get NodeName for a running pipeline job ?
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-38282) Actions contain duplicate "_class" property
Title: Message Title Vivek Pandey resolved as Cannot Reproduce Looks like it got fixed along the way. https://ci.blueocean.io/blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject&filter=no-folders&start=0&limit=26 shows only one _class for action. Jenkins / JENKINS-38282 Actions contain duplicate "_class" property Change By: Vivek Pandey Status: Open Resolved Resolution: Cannot Reproduce 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 Grou
[JIRA] (JENKINS-41372) Blue Ocean pagination API's "Link" response header contains duplicate "start" and "limit" params
Title: Message Title Vivek Pandey updated JENKINS-41372 Jenkins / JENKINS-41372 Blue Ocean pagination API's "Link" response header contains duplicate "start" and "limit" params Change By: Vivek Pandey Status: In Progress Review 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-34581) Please add support for Pipelines to the Powershell plugin
Title: Message Title Gabriel Loewen commented on JENKINS-34581 Re: Please add support for Pipelines to the Powershell plugin I have added powershell support to the durable task plugin, and I am currently testing it. I will respond to this thread once I am ready to submit a PR. 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-42520) Header content wraps
Title: Message Title Josh McDonald commented on JENKINS-42520 Re: Header content wraps https://github.com/jenkinsci/blueocean-plugin/pull/888 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-40143) Duplicate email with Extended E-mail Notification
Title: Message Title David van Laatum commented on JENKINS-40143 Re: Duplicate email with Extended E-mail Notification What about the job xml? any differences between new and old jobs that are configured the same way? 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-42527) Stage view overlapping durations
Title: Message Title
Owen Wood updated an issue
Jenkins / JENKINS-42527
Stage view overlapping durations
Change By:
Owen Wood
Using the following Pipeline to reproduce: ``` {code:java} node \ {stage concurrency: 1, name: "mult plat copy"sh "echo abc"stage concurrency: 1, name: "big data entry"sh "echo "stage concurrency: 1, name: "big data 1 entry"sh "echo"stage concurrency: 1, name: "big data entry2"sh "echo 123"stage concurrency: 1, name: "big data entry3"sh "echo"stage concurrency: 1, name: "big data entry4"sh "echo"stage concurrency: 1, name: "big data entry5"sh "echo"stage concurrency: 1, name: "big data entry6"sh "echo"stage concurrency: 1, name: "big data entry7"sh "echo"stage concurrency: 1, name: "big data entry8"sh "echo"stage concurrency: 1, name: "big data entry9"sh "echo; sleep 60"stage concurrency: 1, name: "check big data"sh "echo; sleep 70"stage concurrency: 1, name: "check big data2"sh "echo; sleep 80"stage concurrency: 1, name: "check big data3"sh "echo"} {code} ``` Note the overlapping duration in the screenshot ! attached ( image-2017-03-07-10-52-30-498.png ! )
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42527) Stage view overlapping durations
Title: Message Title
Owen Wood created an issue
Jenkins / JENKINS-42527
Stage view overlapping durations
Issue Type:
Bug
Assignee:
Sam Van Oort
Attachments:
image-2017-03-07-10-52-30-498.png
Components:
pipeline-stage-view-plugin
Created:
2017/Mar/07 12:54 AM
Environment:
Jenkins Version: 2.32 PIpeline plugins: pipeline-build-step:2.4:not-pinned pipeline-github-lib:1.0:not-pinned pipeline-graph-analysis:1.3:not-pinned pipeline-input-step:2.5:not-pinned pipeline-milestone-step:1.3:not-pinned pipeline-model-api:1.0:not-pinned pipeline-model-declarative-agent:1.0:not-pinned pipeline-model-definition:1.0:not-pinned pipeline-rest-api:2.4:not-pinned pipeline-stage-step:2.2:not-pinned pipeline-stage-tags-metadata:1.0:not-pinned pipeline-stage-view:2.4:not-pinned
Priority:
Minor
Reporter:
Owen Wood
Using the following Pipeline to reproduce: ``` node { stage concurrency: 1, name: "mult plat copy" sh "echo abc" stage concurrency: 1, name: "big data entry" sh "echo " stage concurrency: 1, name: "big data 1 entry" sh "echo" stage concurrency: 1, name: "big data entry2" sh "echo 123" stage concurrency: 1, name: "big data entry3" sh "echo" stage concurrency: 1, name: "big data entry4" sh "echo" stage concurrency: 1, name: "big data entry5" sh "echo" stage concurrency: 1, name: "big data entry6" sh "echo" stage concurrency: 1, name: "big data entry7" sh "echo" stage concurrency: 1, name: "big data entry8" sh "echo" stage concurrency: 1, name: "big data entry9" sh "echo; sleep 60" stage concurrency: 1, name: "check big data" sh "echo; sleep 70" stage concurrency:
[JIRA] (JENKINS-42525) Regression upgrading to workflow-multibranch 2.13 from 2.12
Title: Message Title Jesse Glick resolved as Won't Fix You need to checkout scm if you want to get changelogs. See the release notes, and update your tests. We already discussed this in the context of the 2.11 release weeks ago. Jenkins / JENKINS-42525 Regression upgrading to workflow-multibranch 2.13 from 2.12 Change By: Jesse Glick Status: Open Resolved Resolution: Won't Fix 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
[JIRA] (JENKINS-42032) Support for Pull request testing by trigger
Title: Message Title Michael Neale commented on JENKINS-42032 Re: Support for Pull request testing by trigger Stephen Connolly they are currently using GHPRB which allows this it seems - so it isn't burning up API right now (that may be just luck?) 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-42511) Branch indexing creates duplicate copies of branch projects
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-42511 Branch indexing creates duplicate copies of branch projects Change By: Jesse Glick Summary: ISE from RunMap.put Branch indexing creates duplicate copies of branch projects 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-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title Michael Neale commented on JENKINS-40877 Re: Display links to Github PR and Branch on Pipeline Result The WIP PR: https://github.com/jenkinsci/blueocean-plugin/pull/856 The branch to get the github data in runs: https://github.com/jenkinsci/blueocean-plugin/pull/858 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-36896) Stack Trace on startup
Title: Message Title D S commented on JENKINS-36896 Re: Stack Trace on startup Hi, Just to be clear I followed the steps above to remove the plugin clearing the symlinks is the step after removing the plugin 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-42511) ISE from RunMap.put
Title: Message Title Jesse Glick assigned an issue to Stephen Connolly Jenkins / JENKINS-42511 ISE from RunMap.put Change By: Jesse Glick Assignee: Jesse Glick Stephen Connolly 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-42511) ISE from RunMap.put
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-42511 ISE from RunMap.put Change By: Jesse Glick Priority: Critical Blocker 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-42511) ISE from RunMap.put
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-42511 ISE from RunMap.put Change By: Jesse Glick Labels: pipeline regression 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-41677) Expose display URLs in environment variables
Title: Message Title James Dumay commented on JENKINS-41677 Re: Expose display URLs in environment variables Steven Gardell would you mind creating a new bug for that please? 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-42511) ISE from RunMap.put
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-42511 ISE from RunMap.put Change By: Jesse Glick Component/s: branch-api-plugin Component/s: core 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-42526) Add ability to restrict access to maven job's 'Artifactory Release Staging
Title: Message Title suresh nallamilli created an issue Jenkins / JENKINS-42526 Add ability to restrict access to maven job's 'Artifactory Release Staging Issue Type: Improvement Assignee: Eyal Ben Moshe Components: artifactory-plugin Created: 2017/Mar/07 12:08 AM Priority: Minor Reporter: suresh nallamilli In Jenkins job configuration - for 'project based security' option add the ability to restrict access to maven jobs's artifactory release staging. We have around 12k Jenkins jobs and at global level every logged in user has permissions for artifactory release staging option. We would like to restrict that option for selected Jenkins jobs so that only authorized users can do a release build Add Comment
[JIRA] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Matt Hauck commented on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use Woot! :sparkles: 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-42525) Regression upgrading to workflow-multibranch 2.13 from 2.12
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-42525 Regression upgrading to workflow-multibranch 2.13 from 2.12 Issue Type: Bug Assignee: Unassigned Components: workflow-multibranch-plugin Created: 2017/Mar/07 12:05 AM Priority: Major Reporter: Vivek Pandey One of BO multi-branch test related to change sets fails with workflow-multibranch 2.13. The test checks out local git repo, runs, makes 4 commits and expects 4 change sets. Test is at: https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/test/java/io/jenkins/blueocean/rest/impl/pipeline/MultiBranchTest.java#L541. Suspect seems to be https://github.com/jenkinsci/workflow-multibranch-plugin/commit/f42d04620309ccfb11c58e7ccf72d0cea490094f. Based on what this test is doing, it appears local git repo changes won't be picked up with workflow-multibranch 2.13. Add Comment
[JIRA] (JENKINS-42473) Cannot get property 'stages' on null object
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42473 Re: Cannot get property 'stages' on null object Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/Converter.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/bd692a56a92193d4a2fe74423a4435836709fc92 Log: [FIXED JENKINS-42473] Only do parsing if WorkflowScript Deals with cases where there are multiple SourceUnits in the CompilationUnit. 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-42473) Cannot get property 'stages' on null object
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42473 Re: Cannot get property 'stages' on null object Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/Utils.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/Converter.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/944d34f7b8269380b43a94f1e63e750c6c33 Log: JENKINS-42473 Use a better way of getting the flow execution Not sure yet if this will actually solve the problem, but it seems superior regardless. I lifted this from ReplayAction. 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-42473) Cannot get property 'stages' on null object
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42473 Re: Cannot get property 'stages' on null object Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/pom.xml pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BasicModelDefTest.java pom.xml http://jenkins-ci.org/commit/pipeline-model-definition-plugin/b4bd7fd29639c3bc95902d61bdf60c4e5f4203fb Log: Reproduce JENKINS-42473 failure. Required bumping git plugin version, running in a folder, and making the git plugin a direct dependency rather than a test dependency. phew. 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-42473) Cannot get property 'stages' on null object
Title: Message Title Andrew Bayer updated JENKINS-42473 Jenkins / JENKINS-42473 Cannot get property 'stages' on null object Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed 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-42450) Efficiently add a single repo to a github org without requiring a full scan
Title: Message Title Michael Neale assigned an issue to Vivek Pandey Jenkins / JENKINS-42450 Efficiently add a single repo to a github org without requiring a full scan Change By: Michael Neale Assignee: Stephen Connolly Vivek Pandey 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-42524) Don't blacklist GStringImpl from XStream serialization
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-42524 Don't blacklist GStringImpl from XStream serialization Issue Type: Improvement Assignee: Unassigned Components: remoting Created: 2017/Mar/06 11:58 PM Priority: Minor Reporter: Andrew Bayer So I wanted to discuss this, in case there's a good reason for rejecting org.codehaus.groovy.runtime.GStringImpl specifically. We're currently blacklisting org.codehaus.groovy.runtime.* in hudson.remoting.ClassFilter.DEFAULT and that can cause hassles, so I thought it was worth discussion. Add Comment
[JIRA] (JENKINS-42523) Pipeline editor does not work when user is logged out
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42523 Pipeline editor does not work when user is logged out Change By: James Dumay Summary: Pipeline editor does not work when user is logged out 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-42523) Pipeline editor does not work when logged out
Title: Message Title James Dumay created an issue Jenkins / JENKINS-42523 Pipeline editor does not work when logged out Issue Type: Bug Assignee: Keith Zantow Attachments: editor.png Components: blueocean-plugin Created: 2017/Mar/06 11:54 PM Priority: Critical Reporter: James Dumay Steps to reproduce Go to blueocean.io and log out Click "Pipeline editor" Click "Save" The editor save dialog will not open. There is a 403 in the console. Questions Can the editor be used on a Jenkins without authentication? If the editor cant be used by anonymous users with authentication enabled, then we need to prevent users from entering the editor in this case.
[JIRA] (JENKINS-42394) Error loading shared library (404 on BitBucket) during a replay of a previous build
Title: Message Title
Patrick Miller commented on JENKINS-42394
Re: Error loading shared library (404 on BitBucket) during a replay of a previous build
We are also experiencing this issue in our Jenkins environment at PrinterLogic. Let me know if I can provide any additional information. To reproduce issue just replay any build that contains a global pipeline library. A new build will not error out when fetching the global library from bitbucket. Versions
Bitbucket Branch Source Plugin 1.9
Branch API Plugin 1.11.1
Jenkins 2.19.4
Pipeline 2.4
Pipeline: Shared Groovy Libraries 2.5
SCM API Plugin 1.3
Jenkinsfile Header
#!groovy
@Library('printerlogic@develop') _
// ... pipeline script
Console Output
Replayed #3
Loading library shared-scripts@develop
> git rev-parse --is-inside-work-tree # timeout=10
Setting origin to https://bitbucket.org/XXX/jenkins-scripts.git
> git config remote.origin.url https://bitbucket.org/XXX/jenkins-scripts.git # timeout=10
Fetching origin...
Fetching upstream changes from origin
> git --version # timeout=10
using GIT_ASKPASS to set credentials x account on Bitbucket
> git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
> git rev-parse develop^{commit} # timeout=10
> git rev-parse origin/develop^{commit} # timeout=10
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://bitbucket.org/XXX/jenkins-scripts.git # timeout=10
Fetching upstream changes from https://bitbucket.org/XXX/jenkins-scripts.git
> git --version # timeout=10
using GIT_ASKPASS to set credentials x account on Bitbucket
> git fetch --tags --progress https://bitbucket.org/XXX/jenkins-scripts.git +refs/heads/*:refs/remotes/origin/*
Checking out Revision 3dbb0ffbc68f84a85073923c3e3eaa013d9d713b (develop)
> git config core.sparsecheckout # timeout=10
> git checkout -f 3dbb0ffbc68f84a85073923c3e3eaa013d9d713b
> git rev-list 3dbb0ffbc68f84a85073923c3e3eaa013d9d713b # timeout=10
[Bitbucket] Notifying commit build result
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 404: Not Found.
{"type": "error", "error": {"message": "Changeset not found."}}
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postRequest(BitbucketCloudApiClient.java:529)
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postRequest(BitbucketCloudApiClient.java:556)
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postBuildStatus(BitbucketCloudApiClient.java:321)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketChangesetCommentNotifier.buildStatus(BitbucketChangesetCommentNotifier.java:49)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications.createBuildCommitStatus(BitbucketBuildStatusNotifications.java:87)
at com.cloudbees.jenkins.p
[JIRA] (JENKINS-42522) Metadata plugin deletes old data on startup
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-42522 Metadata plugin deletes old data on startup Issue Type: Bug Assignee: rsandell Components: metadata-plugin Created: 2017/Mar/06 11:53 PM Priority: Critical Reporter: Steven Christou The metadata plugin will delete old data content at the start of Jenkins. In order to re-build the metadata information the plugin triggers a save operation (https://github.com/jenkinsci/metadata-plugin/blob/master/src/main/java/com/sonyericsson/hudson/plugins/metadata/contributors/JobContributorsController.java#L89-L91) at the start of Jenkins for each job. Because of this save operation it will delete any old data and override it. There should be a way to trigger the rebuilding of metadata information without having to perform a save operation at the start of Jenkins. Add Comment
[JIRA] (JENKINS-42521) RunWrapper should have a "getCurrentResult()" method
Title: Message Title Andrew Bayer commented on JENKINS-42521 Re: RunWrapper should have a "getCurrentResult()" method PR up at https://github.com/jenkinsci/workflow-support-plugin/pull/31 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-42521) RunWrapper should have a "getCurrentResult()" method
Title: Message Title Andrew Bayer updated JENKINS-42521 Jenkins / JENKINS-42521 RunWrapper should have a "getCurrentResult()" method Change By: Andrew Bayer Status: In Progress Review 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-42521) RunWrapper should have a "getCurrentResult()" method
Title: Message Title Andrew Bayer started work on JENKINS-42521 Change By: Andrew Bayer Status: Open In Progress 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-42521) RunWrapper should have a "getCurrentResult()" method
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-42521 RunWrapper should have a "getCurrentResult()" method Issue Type: Improvement Assignee: Andrew Bayer Components: workflow-support-plugin Created: 2017/Mar/06 11:43 PM Priority: Minor Reporter: Andrew Bayer Specifically, I think it makes sense to have a RunWrapper.getCurrentResult() method that never returns null. That is, it should return Result.SUCCESS if run.getResult() is null, since users consistently get confused by RunWrapper.getResult() returning null. Add Comment
[JIRA] (JENKINS-42498) Declarative Pipeline serialization errors when XStreamPickle is used
Title: Message Title Andrew Bayer commented on JENKINS-42498 Re: Declarative Pipeline serialization errors when XStreamPickle is used After initial review, I tried an alternate approach, which is up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/132 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-42520) Header content wraps
Title: Message Title Josh McDonald started work on JENKINS-42520 Change By: Josh McDonald Status: Open In Progress 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-42511) ISE from RunMap.put
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-42511 ISE from RunMap.put Change By: Jesse Glick Assignee: Jesse Glick 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-42511) ISE from RunMap.put
Title: Message Title Jesse Glick started work on JENKINS-42511 Change By: Jesse Glick Status: Open In Progress 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-42511) ISE from RunMap.put
Title: Message Title Jesse Glick commented on JENKINS-42511 Re: ISE from RunMap.put Happens sporadically, but often enough to do diagnosis I think. 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-42520) Header content wraps
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42520 Header content wraps Change By: James Dumay Priority: Minor Major 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-42520) Header content wraps
Title: Message Title James Dumay created an issue Jenkins / JENKINS-42520 Header content wraps Issue Type: Bug Assignee: Josh McDonald Attachments: header.png Components: blueocean-plugin Created: 2017/Mar/06 11:32 PM Priority: Minor Reporter: James Dumay If the branch or any other content here gets too long (like changes) we should not overflow and ellipse. Add Comment
[JIRA] (JENKINS-26143) Workflow Snippet Generator - Incorrect format for Input with Choice Parameter
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-26143 Workflow Snippet Generator - Incorrect format for Input with Choice Parameter Change By: Jesse Glick Assignee: Jesse Glick 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-42511) ISE from RunMap.put
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-42511 ISE from RunMap.put I saw this get thrown from workflow-aggregator-plugin/demo … jenkins.model.lazy.LazyBuildMixIn newBuild WARNING: A new build could not be created in job cd/master java.lang.IllegalStateException: JENKINS-23152: /var/jenkins_home/jobs/cd/branches/master/builds/1 already existed; will not overwrite with cd/master #1 at hudson.model.RunMap.put(RunMap.java:188) at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:185) at org.jenkinsci.plugins.workflow.job.WorkflowJob.createExecutable(WorkflowJob.java:260) at hudson.model.Executor$1.call(Executor.java:355) at hudson.model.Executor$1.call(Executor.java:337) at hudson.model.Queue._withLock(Queue.java:1368) at hudson.model.Queue.withLock(Queue.java:1229) at hudson.model.Executor.run(Executor.java:337) but could not reproduce it—the next time I started the container, all was fine. I have not yet figured out what could cause this. Something has to be deeply wrong for this to happen—for example, two Job’s with the same name. I have a suspicion that something in the SCM API 2.x changes caused this. Stephen Connolly any clues? Change By: Jesse Glick Summary: a job has a build but no history ISE from RunMap . put Priority: Minor Critical Labels: core pipeline Add Comment
[JIRA] (JENKINS-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title Michael Neale assigned an issue to Ivan Meredith Jenkins / JENKINS-40877 Display links to Github PR and Branch on Pipeline Result Change By: Michael Neale Assignee: Thorsten Scherler Ivan Meredith 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-41833) Update table design
Title: Message Title Josh McDonald commented on JENKINS-41833 Re: Update table design Should probably stay in "in progress", only the pipelines page has been updated. 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-41833) Update table design
Title: Message Title Michael Neale updated JENKINS-41833 Jenkins / JENKINS-41833 Update table design Change By: Michael Neale Status: In Progress Review 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-34825) Jobs in Folders should show credentials bound in the credential domain
Title: Message Title Allan BURDAJEWICZ updated JENKINS-34825 Jenkins / JENKINS-34825 Jobs in Folders should show credentials bound in the credential domain Change By: Allan BURDAJEWICZ Status: In Progress Review 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-42385) Clean up JDL css colours
Title: Message Title Josh McDonald commented on JENKINS-42385 Re: Clean up JDL css colours I'll duplicate what I wrote there - I would like to change the JDL so we're publishing pre-transform, just a compilation of .JSX and .less files, with the tests and stories stripped out. We'd get a lot of benefits, not just the ability to easily reference the css theme and mixins, but Idea would be able to make sense of the module for completion / error highlighting, instead of the jumbled mess you get from Babel which for some reason Idea won't parse. 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-36858) Allow plugins to consume the less from the JDL
Title: Message Title Josh McDonald commented on JENKINS-36858 Re: Allow plugins to consume the less from the JDL To be honest, I'd like to remove all transforms from the JDL build process, and publish as JSX + Less. 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-41974) variable replacement does not work as expected with some variable names
Title: Message Title Gareth Western closed an issue as Fixed (Hopefully) fixed as of 1.5 Jenkins / JENKINS-41974 variable replacement does not work as expected with some variable names Change By: Gareth Western Status: Resolved Closed 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-41974) variable replacement does not work as expected with some variable names
Title: Message Title Gareth Western resolved as Fixed Jenkins / JENKINS-41974 variable replacement does not work as expected with some variable names Change By: Gareth Western Status: Open Resolved Assignee: Matthieu Huin Gareth Western Resolution: Fixed 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-40574) Pipeline build parameters are null in first build
Title: Message Title Paul LeTang commented on JENKINS-40574 Re: Pipeline build parameters are null in first build You can get around this by using params.SOME_PARAMETER instead of env.SOME_PARAMETER. 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-42479) New plugin doesn't work with existing credentials
Title: Message Title Claudiu Guiman commented on JENKINS-42479 Re: New plugin doesn't work with existing credentials I think I figured out what went wrong: In the new version, Azure Credentials has a new member of type 'Secret'. While testing, that member was intialized to null, but for some reason, now, it started to get initialized to empty string. I've fixed that and also made http URLs valid in the new Azure Credentials plugin (https://github.com/jenkinsci/azure-credentials-plugin/commit/f6659252e3d531ea927c76c06f86f80ebe0ae9fd) The plugin should be release in a few days and VMAgents will start consuming it very soon after 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-31946) Parameter expression may only resolve to a credentials ID
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-31946 Parameter _expression_ may only resolve to a credentials ID Change By: Jesse Glick Assignee: Jesse Glick 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-32402 Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs Change By: Jesse Glick Assignee: Jesse Glick 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-40990) Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail
Title: Message Title Andreas Mandel commented on JENKINS-40990 Re: Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail Oleg Nenashev thanks for the feedback. Basically I've explained it all above already, so I try to give it some more detail. I see 2 things here the one is the JDK which is required to run Jenkins master or the nodes and the JDK required to execute a job. This is very well solved for freestyle jobs, where I can even execute a JDK1.4 build with a recent Jenkins running on Java 8. But it is broken now with the maven job type (which I know is evil, not only for that reason). IMHO it is essential that the JDK that powers Jenkins in unrelated to the JDK that performs the build. We can build any old Visual Basic software but fail with a old Java maven build? The maven plugin requires JDK1.6 and 1.7 since a long time - before the change to remoting 3.0. This is the reason why the maven plugin switches the execution JDK to the platform JDK and points compiler etc. to the old JDK (see the linked code change in my comment above). This switch now does not work any more and must be repaired to function again. The main question is why the root cause exception UnsupportedClassVersionError is not visible any more to the caller of Channel.call(...), and how we can make this visible again. If this is not possible there should be a other solution, Please note that this issue will hit projects bound to Java 7 also, once Jenkins requires Java 8. 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 unsub
[JIRA] (JENKINS-42450) Efficiently add a single repo to a github org without requiring a full scan
Title: Message Title James Dumay commented on JENKINS-42450 Re: Efficiently add a single repo to a github org without requiring a full scan Stephen Connolly could you give us an example of how to do that please? cc Vivek Pandey 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-42001) Blue Ocean logo should be Jenkins
Title: Message Title Ivan Meredith started work on JENKINS-42001 Change By: Ivan Meredith Status: Open In Progress 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-42206) No selection state for "where do you store your code"
Title: Message Title Ivan Meredith updated JENKINS-42206 Jenkins / JENKINS-42206 No selection state for "where do you store your code" Change By: Ivan Meredith Status: In Review Resolved Resolution: Fixed 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-42254) multibranch pipeline job notified by github, but repo scan finds "No changes detected"
Title: Message Title Stephen Connolly started work on JENKINS-42254 Change By: Stephen Connolly Status: Open In Progress 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-42254) multibranch pipeline job notified by github, but repo scan finds "No changes detected"
Title: Message Title Stephen Connolly updated JENKINS-42254 Jenkins / JENKINS-42254 multibranch pipeline job notified by github, but repo scan finds "No changes detected" Change By: Stephen Connolly Status: In Progress Review 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-42254) multibranch pipeline job notified by github, but repo scan finds "No changes detected"
Title: Message Title Stephen Connolly assigned an issue to Stephen Connolly Jenkins / JENKINS-42254 multibranch pipeline job notified by github, but repo scan finds "No changes detected" Change By: Stephen Connolly Assignee: Stephen Connolly 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-42254) multibranch pipeline job notified by github, but repo scan finds "No changes detected"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42254 Re: multibranch pipeline job notified by github, but repo scan finds "No changes detected" Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java src/main/java/org/jenkinsci/plugins/github_branch_source/PullRequestGHEventSubscriber.java src/main/java/org/jenkinsci/plugins/github_branch_source/PushGHEventSubscriber.java http://jenkins-ci.org/commit/github-branch-source-plugin/92e38ad8e6ded68a6200639936e45534a4fe7076 Log: JENKINS-42254 Make the github sync delay configurable 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-42496) Pipeline support
Title: Message Title Bruno P. Kinoshita commented on JENKINS-42496 Re: Pipeline support Hi Martin, for the near future, only if we get a pull request, or if I get a customer using TestLink. At the moment I am not using TestLink, so cannot spend much of my $work or spare time on the plug-in. However, should someone submits a pull request, I'd be happy to stop 15 minutes or so, review the work and maybe cut a new release. Cheers Bruno 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-42517) SCM API 2.x is leaking github connections
Title: Message Title R. Tyler Croy commented on JENKINS-42517 Re: SCM API 2.x is leaking github connections Ah wunderbar! Do you know if this is actually leaking connections/descriptors or not? I'm trying to decide whether I should upgrade this plugin now or if it can wait until the next time I get some more updates to install (usually once every couple weeks) 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-42450) Efficiently add a single repo to a github org without requiring a full scan
Title: Message Title Stephen Connolly commented on JENKINS-42450 Re: Efficiently add a single repo to a github org without requiring a full scan You should be firing an event through the SCMEvent API. 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-42387) Ability to add or delete single repository by name
Title: Message Title Stephen Connolly commented on JENKINS-42387 Re: Ability to add or delete single repository by name Webhook solves this on the latest plugins 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-42517) SCM API 2.x is leaking github connections
Title: Message Title Stephen Connolly commented on JENKINS-42517 Re: SCM API 2.x is leaking github connections https://github.com/kohsuke/github-api/pull/346 was the fix btw 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-42517) SCM API 2.x is leaking github connections
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-42517 SCM API 2.x is leaking github connections Change By: Stephen Connolly Component/s: github-api-plugin Component/s: github-branch-source-plugin 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-42498) Declarative Pipeline serialization errors when XStreamPickle is used
Title: Message Title Andrew Bayer commented on JENKINS-42498 Re: Declarative Pipeline serialization errors when XStreamPickle is used PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/131 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-42498) Declarative Pipeline serialization errors when XStreamPickle is used
Title: Message Title Andrew Bayer updated JENKINS-42498 Jenkins / JENKINS-42498 Declarative Pipeline serialization errors when XStreamPickle is used Change By: Andrew Bayer Status: In Progress Review 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-42517) SCM API 2.x is leaking github connections
Title: Message Title Stephen Connolly resolved as Fixed Jenkins / JENKINS-42517 SCM API 2.x is leaking github connections Change By: Stephen Connolly Status: Open Resolved Resolution: Fixed 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-42517) SCM API 2.x is leaking github connections
Title: Message Title Stephen Connolly commented on JENKINS-42517 Re: SCM API 2.x is leaking github connections Fixed in github-api-plugin 1.85 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-41830) SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job
Title: Message Title Stephen Connolly closed an issue as Duplicate Jenkins / JENKINS-41830 SCM - Cloning multiple git repositories in parallel causes same change multiple times in pipeline job Change By: Stephen Connolly Status: Open Closed Resolution: Duplicate 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-42498) Declarative Pipeline serialization errors when XStreamPickle is used
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-42498 Declarative Pipeline serialization errors when XStreamPickle is used Change By: Andrew Bayer Summary: Declarative Pipeline serialization errors when -> _expression_ fails XStreamPickle is used 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-42498) Declarative Pipeline when -> expression fails
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-42498 Declarative Pipeline when -> _expression_ fails Change By: Andrew Bayer Priority: Minor Blocker 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-34973) RejectedAccessException thrown but no pending script approval added
Title: Message Title Jesse Glick commented on JENKINS-34973 Re: RejectedAccessException thrown but no pending script approval added …though if GroovySandbox had an API to set a thread-local ApprovalContext, to be used from StaticWhitelist.blacklist, then SandboxContinuable could pass this rather than inspecting the Outcome, probably increasing reliability. 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-34973) RejectedAccessException thrown but no pending script approval added
Title: Message Title Jesse Glick assigned an issue to Unassigned Possibly I could just make ScriptApproval.accessRejected be automatic at the throw site Actually I cannot—there is no ApprovalContext. Therefore I consider this purely a bug in workflow-cps. Unclear if there is only one mechanism by which this problem might occur, or several. Jenkins / JENKINS-34973 RejectedAccessException thrown but no pending script approval added Change By: Jesse Glick Component/s: script-security-plugin Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42519) Closed pull requests, branch jobs are not cleaned up
Title: Message Title Stephen Ash created an issue Jenkins / JENKINS-42519 Closed pull requests, branch jobs are not cleaned up Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2017/Mar/06 8:10 PM Environment: - Jenkins 2.32.2 LTS - Branch API Plugin 2.0.7 - Git plugin 3.1.0 - GitHub Branch Source Plugin 2.0.3 - Pipeline: Multibranch 2.13 Priority: Minor Reporter: Stephen Ash When I am building a multibranch pipeline job, I am noticing that a lot of jobs in Jenkins are still showing and that their workspaces can still be found on disk (wasting space). It seems like when a github webhook event is received that a PR is closed or a branch is deleted, then those should be cleaned up automatically. Steps: Create multi branch pipeline. Set branch source to GitHub repo. Configure to build all branches and PRs. Create PR, confirm that job runs successfully, etc. Merge PR. ==- From "Scan Repository > Events" [Mon Mar 06 19:49:54 UTC 2017] Received org.jenkinsci.plugins.github_branch_source.PushGHEventSubscriber$SCMHeadEventImpl REMOVED event from 10.50.226.16 ⇒ https:///github-webhook/ with timestamp Mon Mar 06 19:49:49 UTC 2017 ==- Results: PR job shows as disabled (strikethrough) in Jenkins
[JIRA] (JENKINS-37139) 'Build periodically with parameters' option not available for Pipeline jobs
Title: Message Title Nicolas Bernard commented on JENKINS-37139 Re: 'Build periodically with parameters' option not available for Pipeline jobs Hello, Did you guys manage to fix the issue ? This functionality is really great and would definetely be a plus for pipeline scripts. Regards 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-42518) Provide lightweight checkout capability to avoid repository clone for multi-branch pipeline jobs
Title: Message Title Peter Hayes created an issue Jenkins / JENKINS-42518 Provide lightweight checkout capability to avoid repository clone for multi-branch pipeline jobs Issue Type: Improvement Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2017/Mar/06 8:01 PM Priority: Major Reporter: Peter Hayes JENKINS-33273 introduced a lightweight checkout capability to allow SCM implementors to avoid having checkout the scm on the master to read the contents of the Jenkinsfile from the SCM. The comments in that bug mention that git doesn't offer a way to do so but I would think this is possible to do using Bitbucket APIs to read a particular file's contents on a branch. In our use case, our repository is multi-gigabyte and we have many developers working within it creating many branches so cloning the repo on master for every branch is very costly in terms of time and storage. Add Comment
[JIRA] (JENKINS-38813) NullPointerException accessing params variable with Subversion tag
Title: Message Title Christopher Head closed an issue as Fixed Fixed in [https://github.com/jenkinsci/workflow-cps-plugin/commit/2ee7ab7dd9da1b428009c663935a134625890263|2ee7ab7dd9da1b428009c663935a134625890263]. Jenkins / JENKINS-38813 NullPointerException accessing params variable with Subversion tag Change By: Christopher Head Status: Open Closed Resolution: Fixed 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 fro
[JIRA] (JENKINS-38813) NullPointerException accessing params variable with Subversion tag
Title: Message Title Christopher Head edited a comment on JENKINS-38813 Re: NullPointerException accessing params variable with Subversion tag Fixed in [https://github.com/jenkinsci/workflow-cps-plugin/commit/2ee7ab7dd9da1b428009c663935a134625890263|2ee7ab7dd9da1b428009c663935a134625890263]. 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.
