[JIRA] (JENKINS-56966) Azure Deployment of .NET Package Folder has some files with 0 size
Title: Message Title
Josh Chiancone updated an issue
Jenkins / JENKINS-56966
Azure Deployment of .NET Package Folder has some files with 0 size
Change By:
Josh Chiancone
We are building a .NET 4.5 Web API application using the declarative pipelines syntax to issue bat commands calling msbuild /t:clean, build, and package on a Windows 10 slave VM. Package step creates a directory of publishable files at: ./obj/\{config}/Package/PackageTmpFinal step of the pipeline uses the azureWebAppPublish plugin to publish this directory to Azure Web Site. Publish step reports successful, but when looking at the wwwroot/bin folder on the published site, some DLLs have a 0 byte file size. For example, in the build server's PackageTmp folder, A.Library.DLL has file size 1124 KB, but after deploying via the plugin, A.Library.DLL has file size 0 bytes in Azure.Also noticed that the .azure-deploy GIT folder responsible for pushing the deploy files to Azure master contains some unstaged publish files after the pipeline has completed, one of which is the affected A.Library.DLL.Azure Web App Publish Step:{code:java}azureWebAppPublish azureCredentialsId: params.azure_credential_id, resourceGroup: params.resource_group, appName: params.service_name, sourceDirectory: "/obj/${params.build_mode}/Package/PackageTmp"{code}x
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56966) Azure Deployment of .NET Package Folder has some files with 0 size
Title: Message Title
Josh Chiancone updated an issue
Jenkins / JENKINS-56966
Azure Deployment of .NET Package Folder has some files with 0 size
Change By:
Josh Chiancone
We are building a .NET 4.5 Web API application using the declarative pipelines yntax syntax to issue bat commands calling msbuild /t:clean, build, and package on a Windows 10 slave VM. Package step creates a directory of publishable files at: ./obj/\{config}/Package/PackageTmpFinal step of the pipeline uses the azureWebAppPublish plugin to publish this directory to Azure Web Site. Publish step reports successful, but when looking at the wwwroot/bin folder on the published site, some DLLs have a 0 byte file size. For example, in the build server's PackageTmp folder, A.Library.DLL has file size 1124 KB, but after deploying via the plugin, A.Library.DLL has file size 0 bytes in Azure.Also noticed that the .azure-deploy folder contains some unstaged publish files after the pipeline has completed, one of which is the affected A.Library.DLL.Azure Web App Publish Step:{code:java}azureWebAppPublish azureCredentialsId: params.azure_credential_id, resourceGroup: params.resource_group, appName: params.service_name, sourceDirectory: "/obj/${params.build_mode}/Package/PackageTmp"{code}x
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you
[JIRA] (JENKINS-56966) Azure Deployment of .NET Package Folder has some files with 0 size
Title: Message Title
Josh Chiancone created an issue
Jenkins / JENKINS-56966
Azure Deployment of .NET Package Folder has some files with 0 size
Issue Type:
Bug
Assignee:
Azure DevOps
Components:
azure-app-service-plugin
Created:
2019-04-11 04:13
Environment:
Jenkins (v2.150.1) master installed on Azure Linux VM. Jenkins Slave on Azure Windows 10 VM using Java Web Start
Labels:
plugin azure pipeline
Priority:
Minor
Reporter:
Josh Chiancone
We are building a .NET 4.5 application using the declarative pipelines yntax to issue bat commands calling msbuild /t:clean, build, and package on a Windows 10 slave VM. Package step creates a directory of publishable files at: ./obj/{config}/Package/PackageTmp Final step of the pipeline uses the azureWebAppPublish plugin to publish this directory to Azure Web Site. Publish step reports successful, but when looking at the wwwroot/bin folder on the published site, some DLLs have a 0 byte file size. For example, in the build server's PackageTmp folder, A.Library.DLL has file size 1124 KB, but after deploying via the plugin, A.Library.DLL has file size 0 bytes in Azure. Also noticed that the .azure-deploy folder contains some unstaged publish files after the pipeline has completed, one of which is the affected A.Library.DLL. Azure Web App Publish Step:
azureWebAppPublish azureCredentialsId: params.azure_credential_id, resourceGroup:
[JIRA] (JENKINS-56965) How to show the original version in build parameter page
Title: Message Title Frank Chen created an issue Jenkins / JENKINS-56965 How to show the original version in build parameter page Issue Type: Improvement Assignee: Unassigned Components: parameterized-trigger-plugin Created: 2019-04-11 03:10 Priority: Major Reporter: Frank Chen Dear @all, could you share how to get a file content from linux server, and then show its content(for example, previous version info) as build parameter. Thanks in advance. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-56514) Triggering many (100+) concurrent builds causes some builds to not get parameters set
Title: Message Title arash m commented on JENKINS-56514 Re: Triggering many (100+) concurrent builds causes some builds to not get parameters set Rachel Yen Sure. I've created an issue at that github project, https://github.com/jenkinsci/google-compute-engine-plugin/issues/67 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50504) Jenkins is handing out workspaces that are already in use to new jobs
Title: Message Title Jesse Glick updated JENKINS-50504 Jenkins / JENKINS-50504 Jenkins is handing out workspaces that are already in use to new jobs Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.173 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Jesse Glick commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. sakshi sood yes the format has changed. In your second screenshot, everything at or below [junit] is coming from that branch, until the next such mark. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45579) Step to set stage or parallel status
Title: Message Title Jesse Glick commented on JENKINS-45579 Re: Step to set stage or parallel status No, sorry for confusion. I was just sketching an edit to the original example by Kevin Phillips to not rely on a try-catch block, which would be undesirable in this context as it would catch not just nonzero exit status from a script but all sorts of other errors and even build interrupts and timeouts. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title Adam Carroll commented on JENKINS-55438 Re: Allow sequential stages inside parallel in Scripted syntax Thanks Jesse Glick and An Tran for digging into this more! I personally am not concerned whether or not this is a bug or improvement, as long as it is fixed . It does sound a lot like a bug to me, but I do understand the argument for it being an improvement. Whatever the best path to resolution is will be fine with me. Based on the tickets An Tran linked above, it looks like others desire this functionality as well. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43556) Stage View shows incorrect build result
Title: Message Title Chris Wagner commented on JENKINS-43556 Re: Stage View shows incorrect build result This seems to manifest itself when build numbers are re-used. Consider the following scenario: Builds 1-10 all pass, then builds 11-20 all fail, you decide to clean that up once you fix the build. You delete 11-20 and set your next build number to 11. Now the stages view reports failures for 11-20 even though they are now actually successful. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56201) GCE plugin shouldn't cleanup nodes from different jenkins masters
Title: Message Title Rachel Yen commented on JENKINS-56201 Re: GCE plugin shouldn't cleanup nodes from different jenkins masters Thanks to Karol Lassak, we'll have unique identifiers for the different clouds. I'll resolve this with our next release. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52462) SonarQube Diff Parser should read textRange property
Title: Message Title Tobias Redl started work on JENKINS-52462 Change By: Tobias Redl Status: Open In Progress 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Pascal Laporte commented on JENKINS-38641 Re: Milestone step fails to pass due to deleted/future builds having passed Antonio Muñiz Could you please release the plugins version that include this fix? The last version, 1.3.1 is 2 years old. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45579) Step to set stage or parallel status
Title: Message Title
Stuart Rowe edited a comment on JENKINS-45579
Re: Step to set stage or parallel status
[~jglick] is {{unstable}} a step now? I thought it was only a condition for {{post}} in declarative pipelines.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45579) Step to set stage or parallel status
Title: Message Title Stuart Rowe commented on JENKINS-45579 Re: Step to set stage or parallel status Jesse Glick is unstable a step now? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28284) Images for Test Case trends is broken and generate exception
Title: Message Title Matthew Reed commented on JENKINS-28284 Re: Images for Test Case trends is broken and generate exception Manuel Carrasco I also am experiencing this with plugin V3.16. Based on ankur sharma above, I think we should reopen. Please advise. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56514) Triggering many (100+) concurrent builds causes some builds to not get parameters set
Title: Message Title arash m updated an issue Jenkins / JENKINS-56514 Triggering many (100+) concurrent builds causes some builds to not get parameters set Change By: arash m Priority: Minor Major 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45579) Step to set stage or parallel status
Title: Message Title
Jesse Glick commented on JENKINS-45579
Re: Step to set stage or parallel status
stage ('Optional Tests') {
echo 'Running optional tests…'
if (sh(script: 'exit -1', returnStatus: true) != 0) {
unstable 'Optional tests failed…do not propagate failure'
}
}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56964) Expose timeout grace period as configurable
Title: Message Title Jonathan Gray created an issue Jenkins / JENKINS-56964 Expose timeout grace period as configurable Issue Type: Improvement Assignee: Unassigned Components: workflow-basic-steps-plugin Created: 2019-04-10 18:47 Labels: plugin pipeline configuration Priority: Minor Reporter: Jonathan Gray As a job author, I would like the pipeline timeout GRACE_PERIOD exposed as a configurable option so that I can allow for teardown steps that take longer than 5s or 60s. I use the timeout option on a stage, but during the normal course of operations if that timeout engages items in an always post step only get that grace period to complete. For processes with extensive cleanup, you see `Body did not finish within grace period; terminating with extreme prejudice` and it force-kills what's running. This can leave some cleanup process incomplete. I'd like to see an option in the timeout step to specify how long that grace period ought to be. Relevant code link: https://github.com/jenkinsci/workflow-basic-steps-plugin/blob/3ecc7bbd91182e330a23a9e661ae1cdfa2d2b55e/src/main/java/org/jenkinsci/plugins/workflow/steps/TimeoutStepExecution.java#L41
[JIRA] (JENKINS-56858) unable to load plugins
Title: Message Title Yufen Kuo commented on JENKINS-56858 Re: unable to load plugins Yes, I do see the messages when running jenkinsfile-runner with -v option $ /usr/local/git/jenkinsfile-runner/app/target/appassembler/bin/jenkinsfile-runner -v 2.164.1 -p /var/jenkins_home/plugins -f /var/jenkins_home/foo -a param1=Test -a param2=MyTest Running pipeline on jenkins 2.164.1 Downloading jenkins 2.164.1... 1.792 [id=32] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: Step API v2.19 (workflow-step-api) java.io.IOException: Pipeline: Step API v2.19 failed to load. You must update Jenkins from v2.89 to v2.121.1 or later to run this plugin. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:626) at hudson.PluginManager$2$1$1.run(PluginManager.java:513) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1065) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 1.794 [id=52] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: API v2.33 (workflow-api) java.io.IOException: Pipeline: API v2.33 failed to load. You must update Jenkins from v2.89 to v2.121.1 or later to run this plugin. Pipeline: Step API v2.19 failed to load. Fix this plugin first. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) --
[JIRA] (JENKINS-56714) Add unit tests for IssuesChartPortlet
Title: Message Title Ulli Hafner commented on JENKINS-56714 Re: Add unit tests for IssuesChartPortlet I see. What about JENKINS-56613 or JENKINS-54736? These issues should be easier to solve... 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56714) Add unit tests for IssuesChartPortlet
Title: Message Title Andreas Reiser commented on JENKINS-56714 Re: Add unit tests for IssuesChartPortlet Seems like this is another class that's pretty hard to test. I'm not sure how exactly I can stub a history of builds to generate the chart and the _expression_ in the class itself is hard to debug due to streams. I'm not sure how to proceed because I can't really tell what is expected. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Shevek . commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) The active-directory thing is a total red herring. We are affected by this, and we do not and never have used AD. The downgrade to 2.150.1 does work. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55319) Mercurial plugin cannot handle spaces in file names
Title: Message Title Jesse Glick updated JENKINS-55319 Jenkins / JENKINS-55319 Mercurial plugin cannot handle spaces in file names Change By: Jesse Glick Status: Fixed but Unreleased Resolved Released As: 2.6 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56926) Jenkinsfile not found in a subfolder
Title: Message Title Joseph Petersen resolved as Fixed Jenkins / JENKINS-56926 Jenkinsfile not found in a subfolder Change By: Joseph Petersen Status: Open Resolved Resolution: Fixed Released As: v2.4.4 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41791) Build cannot be resumed if parallel was used with Kubernetes plugin
Title: Message Title Jesse Glick updated JENKINS-41791 Jenkins / JENKINS-41791 Build cannot be resumed if parallel was used with Kubernetes plugin Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.66 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52462) SonarQube Diff Parser should read textRange property
Title: Message Title Tobias Redl assigned an issue to Tobias Redl Jenkins / JENKINS-52462 SonarQube Diff Parser should read textRange property Change By: Tobias Redl Assignee: Tobias Redl 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe edited a comment on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) Well if it doesn't , the downgrading to Jenkins LTS 2.150.1 worked on our Test Jenkins, so we have that to fall back to if it doesn't work. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) Well if it doesn't downgrading to Jenkins LTS 2.150.1 worked on our Test Jenkins, so we have that to fall back to if it doesn't work. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Daniel Beck commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) Unsure, may or may not help. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe edited a comment on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) So the workaround -Djenkins.security.seed.UserSeedProperty.disableUserSeed=true will not fix this issue?It says its a workaround for SECURITY-901 which mentioned in the description here caused the regression. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) So the workaround -Djenkins.security.seed.UserSeedProperty.disableUserSeed=true will not fix this issue? It says its a workaround for SECURITY-901 which mentioned in the description caused the regression. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51865) Stage locks are created for skipped stages in declarative pipeline
Title: Message Title
Falko Modler edited a comment on JENKINS-51865
Re: Stage locks are created for skipped stages in declarative pipeline
[~wgc123]{quote}It also doesn’t work because either you hardcore “dummy” and potentially block on it{quote}Those potential blocks/locks are very short-lived. You could also define a pool of multiple "dummy" resources to further reduce the (already very small) impact.So this partial workaround is better than nothing.[~abayer]{quote}You can always put lock or timeout (and any other block-scoped options) in your steps instead.{quote}Unfortunately, this is no solution/workaround for {{post}} blocks. E.g. you lock some external resource/server and in ` {{ post ` }} you want to collect the server's logfiles (regardless of the build status).So IMHO, {{beforeOptions}} is still needed.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51865) Stage locks are created for skipped stages in declarative pipeline
Title: Message Title Falko Modler commented on JENKINS-51865 Re: Stage locks are created for skipped stages in declarative pipeline D Pasto It also doesn’t work because either you hardcore “dummy” and potentially block on it Those potential blocks/locks are very short-lived. You could also define a pool of multiple "dummy" resources to further reduce the (already very small) impact. So this partial workaround is better than nothing. Andrew Bayer You can always put lock or timeout (and any other block-scoped options) in your steps instead. Unfortunately, this is no solution/workaround for post blocks. E.g. you lock some external resource/server and in `post` you want to collect the server's logfiles (regardless of the build status). So IMHO, beforeOptions is still needed. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55319) Mercurial plugin cannot handle spaces in file names
Title: Message Title Jesse Glick updated JENKINS-55319 Jenkins / JENKINS-55319 Mercurial plugin cannot handle spaces in file names Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Daniel Beck commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) The LTS upgrade guide seems to have a workaround for this bug Different issue. You're not even logged in with that one. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Dan Peschman commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) Enabling AD caching worked for us too. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe edited a comment on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I was unaware of the opensuse-stable builds. So this is the Jenkins LTS releases.I tried to downgrade to the 2.150.1 LTS and it worked with our installed plugins. The LTS upgrade guide seems to have a workaround for this bughttps://jenkins.io/doc/upgrade-guide/2.150/ 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title sakshi sood edited a comment on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. Not sure why this ticket is closed. What was the fix ? After upgrading Jenkins the logformat for Pipeline jobs changed. Due to this change it's no longer clear which line belongs to which step. This is a problem when looking at parallel steps. Please check my earlier and now screenshot. Using plugin version 2.31and Jenkins version 2.150.3!earlier.JPG! !now.JPG|thumbnail! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55867) sh step termination is never detected if the wrapper process is killed
Title: Message Title Daniel Zabel commented on JENKINS-55867 Re: sh step termination is never detected if the wrapper process is killed I guess what you want should something lokk like this: pid=$$; ( echo "$pid - $PPID"; ) outputs: 19499 - 11953 where 19499 is the pid of the started sh and 11953 is the pid of the parent process (in this case the wrapper i guess) 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title sakshi sood updated an issue Jenkins / JENKINS-54304 Jobs in parallel dont display the variant they are running. Change By: sakshi sood Attachment: now.JPG Attachment: earlier.JPG 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title sakshi sood updated an issue Jenkins / JENKINS-54304 Jobs in parallel dont display the variant they are running. Change By: sakshi sood Comment: Not sure why this ticket is closed. What was the fix ?After upgrading Jenkins the logformat for Pipeline jobs changed. Due to this change it's no longer clear which line belongs to which step. This is a problem when looking at parallel steps. Please check my earlier and now screenshot. Using plugin version 2.31and Jenkins version 2.150.3!now.JPG! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title sakshi sood commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. Not sure why this ticket is closed. What was the fix ? After upgrading Jenkins the logformat for Pipeline jobs changed. Due to this change it's no longer clear which line belongs to which step. This is a problem when looking at parallel steps. Please check my earlier and now screenshot. Using plugin version 2.31 and Jenkins version 2.150.3 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title sakshi sood updated an issue Jenkins / JENKINS-54304 Jobs in parallel dont display the variant they are running. Change By: sakshi sood Attachment: now.JPG 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title sakshi sood edited a comment on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. Not sure why this ticket is closed. What was the fix ?After upgrading Jenkins the logformat for Pipeline jobs changed. Due to this change it's no longer clear which line belongs to which step. This is a problem when looking at parallel steps. Please check my earlier and now screenshot. Using plugin version 2.31and Jenkins version 2.150.3!earlier.JPG! !now.JPG! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I was unaware of the opensuse-stable builds. So this is the Jenkins LTS releases. I tried to downgrade to the 2.150.1 LTS and it worked with our installed plugins. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe edited a comment on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I cannot find a 2.150.2, mentioned above but 2.150-1.2https://pkg.jenkins.io/opensuse/jenkins-2.150-1.2.noarch.rpmI Just tried to downgrade to 2.149 and it did not go so well, as several plugins do not work now.Our users are having serous serious trouble with slow Jenkins user experience. I hope this can be fixed soon. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Alejandro Jurado Walls commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Here are the steps we are using to reproduce the issue: create a branch commit something create a PR merge the PR with master delete the branch on Github enterprise ui. create a branch with the same name from master, (the branch name is the same as the previous one, but that's ok since we deleted already from the github ui). now if we create another PR using this branch, even it shows up properly on the github UI, a scan in Jenkins shows no Jenkinsfile found thus the new PR could not be built. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55867) sh step termination is never detected if the wrapper process is killed
Title: Message Title Daniel Zabel commented on JENKINS-55867 Re: sh step termination is never detected if the wrapper process is killed seems to be the root cause for 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55867) sh step termination is never detected if the wrapper process is killed
Title: Message Title
Daniel Zabel commented on JENKINS-55867
Re: sh step termination is never detected if the wrapper process is killed
example code to visualize the issue:
pid=$$; { echo "$pid - $$"; }
outputs:
11953 - 11953
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Daniel Beck commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) https://pkg.jenkins.io/opensuse-stable/ 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Maximilian Weig assigned an issue to Jesse Glick Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Maximilian Weig Assignee: A. Jesse Jiryu Davis Glick 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Maximilian Weig assigned an issue to A. Jesse Jiryu Davis Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Maximilian Weig Assignee: Maximilian Weig A. Jesse Jiryu Davis 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Maximilian Weig assigned an issue to Maximilian Weig Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Maximilian Weig Assignee: Jesse Glick Maximilian Weig 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Sverre Moe commented on JENKINS-56243 Re: Jenkins GUI is slow -removing cookie fixes it (temporarily) I cannot find a 2.150.2, mentioned above but 2.150-1.2 https://pkg.jenkins.io/opensuse/jenkins-2.150-1.2.noarch.rpm I Just tried to downgrade to 2.149 and it did not go so well, as several plugins do not work now. Our users are having serous trouble with slow Jenkins user experience. I hope this can be fixed soon. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title sakshi sood edited a comment on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. Not sure why this ticket is closed. What was the fix ? We are still not able to see After upgrading Jenkins the branch names in console logs logformat for Pipeline jobs changed . I mean its visible at the start of the step but not in the complete console log which makes Due to this change it difficult 's no longer clear which line belongs to find out on which step I am on . This is a problem when looking at parallel steps. Please check my earlier and now screenshot. Using plugin version 2.31and Jenkins version 2.150.3!earlier.JPG!!now.JPG! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title sakshi sood commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. Not sure why this ticket is closed. What was the fix ? We are still not able to see the branch names in console logs. I mean its visible at the start of the step but not in the complete console log which makes it difficult to find out on which step I am on. Please check my earlier and now screenshot. Using plugin version 2.31 and Jenkins version 2.150.3 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title sakshi sood updated an issue Jenkins / JENKINS-54304 Jobs in parallel dont display the variant they are running. Change By: sakshi sood Attachment: earlier.JPG 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title sakshi sood updated an issue Jenkins / JENKINS-54304 Jobs in parallel dont display the variant they are running. Change By: sakshi sood Attachment: now.JPG 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56963) /pipeline-syntax/ should support url for sharing
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56963 /pipeline-syntax/ should support url for sharing Issue Type: New Feature Assignee: Unassigned Components: workflow-cps-plugin Created: 2019-04-10 15:07 Priority: Minor Reporter: Josh Soref I want to share a url something like: https://ci.jenkins.io/pipeline-syntax/#expr=retry(2) With the result being that: https://ci.jenkins.io/pipeline-syntax/ loads w/ Sample Step set to retry and Retry Count set to 2. I'm flexible about the precise syntax Second example: https://ci.jenkins.io/pipeline-syntax/#expr=readJSON(file:'x',text:'y') With the result being that: https://ci.jenkins.io/pipeline-syntax/ loads w/ Sample Step set to readJSON, File set to x, and FText set to y. And part two of this: Next to the Generate Pipeline Script button there should be a Share this script button, it could be a link-symbol or a share-icon.
[JIRA] (JENKINS-56959) Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-56959 Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel Change By: Mark Waite Component/s: core Component/s: git-plugin 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56959) Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel
Title: Message Title Mark Waite commented on JENKINS-56959 Re: Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel Thanks for the answers. I suspect that means you want the workflow scm step plugin since it provides the changelog: false keyword. I've removed the git plugin and core from the component list. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28119) Link to log of failed step
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28119 Link to log of failed step Not really. I suppose I could revisit this, given the high vote count. Change By: Jesse Glick Labels: stalled-pr 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56959) Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel
Title: Message Title hariprasad Narnavara, commented on JENKINS-56959 Re: Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel Hello Mark Waite, Thank for the quick response. We are doing the more verbose checkout using the cipa library (https://github.com/shasait/cipa/blob/master/src/de/hasait/cipa/activity/CheckoutActivity.groovy). Our multiple checkouts include: Checkout of current revision which has triggered the build Checkout of previous revision (which is tagged for release) to compare the Data Changes. Also pipeline source checkouts. Out of these 3 checkout's we set changelog:false for the previous tagged revision checkout, Since the changes from this changelog are not required. But our job is somehow picking up the changelog from the Previous Build. and we are not doing checkout of previous revision. Our Concerns are: The Duplicate changelog is presented in the User Interface of the job. The email trigger is sent to all the users of the duplicated changelog, when there is a test failures/build failures. We are not using the Git Changelog plugin for this since it just display the detailed changelog and doesn't fix our issue. I hope you i am able to answer all yours questions. Please recommend if this has issue is with specific plugin Since we are not sure what is causing this duplicates and how jenkins changelog works when we are performing multiple checkouts. Thanks, Hariprasad Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56959) Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel
Title: Message Title hariprasad Narnavara, commented on JENKINS-56959 Re: Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel Hello Mark Waite, Thank for the quick response. We are doing the more verbose checkout using the cipa library (https://github.com/shasait/cipa/blob/master/src/de/hasait/cipa/activity/CheckoutActivity.groovy). Our multiple checkouts include: Checkout of current revision which has triggered the build Checkout of previous revision (which is tagged for release) to compare the Data Changes. Also pipeline source checkouts. Out of these 3 checkout's we set changelog:false for the previous tagged revision checkout, Since the changes from this changelog are not required. But our job is somehow picking up the changelog from the Previous Build. and we are not doing checkout of previous revision. Our Concerns are: The Duplicate changelog is presented in the User Interface of the job. The email trigger is sent to all the users of the duplicated changelog, when there is a test failures/build failures. We are not using the Git Changelog plugin for this since it just display the detailed changelog and doesn't fix our issue. I hope you i am able to answer all yours questions. Please recommend if this has issue is with specific plugin Since we are not sure what is causing this duplicates and how jenkins changelog works when we are performing multiple checkouts. Thanks, Hariprasad Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56858) unable to load plugins
Title: Message Title Evaristo Gutierrez commented on JENKINS-56858 Re: unable to load plugins Yufen Kuo could you please check if you can see these messages in the logs? "Running pipeline on jenkins 2.164.1" "Downloading jenkins 2.164.1" Thanks! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56960) Not compatible with native bitbucket server events
Title: Message Title Kyle Rotte created an issue Jenkins / JENKINS-56960 Not compatible with native bitbucket server events Issue Type: Bug Assignee: Unassigned Components: bitbucket-plugin Created: 2019-04-10 14:13 Priority: Blocker Reporter: Kyle Rotte Multiple pull requests exist out there to fix this issue, but nobody with permissions is maintaining the plugin and accepting the pull requests. Since the plugin doesn't understand the events it seriously limits the usefulness of the plugin. The plugin does not handle native Bitbucket Server events. For some reason Atlassian decided to use different event ids Bitbucket Server and Bitbucket Cloud. Add Comment
[JIRA] (JENKINS-56959) Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel
Title: Message Title Mark Waite commented on JENKINS-56959 Re: Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel You mention that "changelog is set to false for the previous revision checkout". In what context is changelog set to false? For example, did you use a command like the following in your Pipeline: git changelog: false, url: 'https://github.com/MarkEWaite/jenkins-bugs.git' or did you use the more verbose checkout syntax like this: checkout changelog: false, scm: [$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CloneOption', honorRefspec: true, noTags: true, reference: '/var/lib/git/mwaite/bugs/jenkins-bugs.git', shallow: false]], gitTool: 'Default', submoduleCfg: [], userRemoteConfigs: [[refspec: '+refs/heads/master:refs/remotes/origin/master', url: 'https://github.com/MarkEWaite/jenkins-bugs']]] In the workflow scm step plugin README, it says: By default each build will show changes from the previous build in its changelog as usual, and you can see an overall changelog on the project index page. You may specify changelog: false to disable changelog generation if it is not of interest, or too large to compute efficiently. Based on that text from the README, I would have assumed that your decision to set changelog to false means that the changelog is not being computed. If it is not being computed, then it may repeat or not repeat or be useful or not useful. If the changelog is important to you, why did you disable changelog generation? Based on the phrasing of the bug report, I think you want this to be assigned to the workflow-scm-step plugin, rather than assigning it to core, git plugin, and workflow-scm-step plugins. However, I'm not entirely sure that is the case. Is your concern about the duplication of the build data that is presented in the user interface for the job? In the example you gave, I assume that build 9 had completed before build 10 started, so you were expecting that "Added validation - User3" would not appear in the changelog for build 10 since it was already included in the completed and successful build 9. Is your concern about the results in a change log generated by the git changelog plugin? Please provide more details so that others can understand what you are expecting and how to duplicate the problem.
[JIRA] (JENKINS-56959) Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-56959 Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel Change By: Mark Waite Assignee: Mark Waite 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55516) Time zone is not allowing in Build periodically with parameters
Title: Message Title Baptiste Mathus commented on JENKINS-55516 Re: Time zone is not allowing in Build periodically with parameters No, not really unfortunately. I'm lacking time to implement this kind of thing. But I'm happy to review a pull request on https://github.com/jenkinsci/parameterized-scheduler-plugin if you can propose it. Thanks! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56959) Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel
Title: Message Title hariprasad Narnavara, created an issue Jenkins / JENKINS-56959 Duplicate ChangeLog on Jenkins builds even though builds are not executed in parallel Issue Type: Bug Assignee: Mark Waite Components: core, git-plugin, workflow-scm-step-plugin Created: 2019-04-10 13:15 Environment: Jenkins ver. 2.121.3 Git Changelog plugin version 2.16 git-client 2.7.0 git 3.7.1 Priority: Critical Reporter: hariprasad Narnavara, The Git ChangeLog's are repeated in the builds as shown below example. Note: We are doing checkout of the previous revision to do the comparision of scripts. But the changelog is set to false for the previous revision checkout. Hence it shows multiple "Git Build Data". But Change log is repeating somehow for every next build executed, even though the next build is executed after 2 days. Example ChangeLog #12 (Jan 31, 2019 8:00:00 AM) [JIRA-XXX]: Added validation — User3 [JIRA-XXX]: Code Clean up — User1 [JIRA-XXX]: Cleanup — User2 [JIRA-XXX]: State model and final cleanup - User1 #10 (Jan 28, 2019 8:00:00 AM) [JIRA-XXX]: Added validation — User3 [JIRA-XXX]: Code Clean up — User1 [JIRA-XXX]: Cleanup — User2 #9 (Jan 27, 2019 8:00:00 AM) [JIRA-XXX]: Added validation — User3
[JIRA] (JENKINS-56958) Add "or gate" functionality to parallel stage in pipeline
Title: Message Title Ozgun Akalin created an issue Jenkins / JENKINS-56958 Add "or gate" functionality to parallel stage in pipeline Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2019-04-10 13:06 Labels: pipeline parallel status Priority: Minor Reporter: Ozgun Akalin Currently, a stage that contains parallel builds is successful if all builds inside the parallel block are successful. We have faced certain scenarios where we would like the pipeline to move to next stage if at least on of the builds is successful. This could be normally achieved by managing the parallel build itself and its builds in try/catch blocks and setting/checking flags. However, due to JENKINS-26522, marking a stage as successful, when it is actually not, is not possible. Add Comment
[JIRA] (JENKINS-55516) Time zone is not allowing in Build periodically with parameters
Title: Message Title siva krishna jampani commented on JENKINS-55516 Re: Time zone is not allowing in Build periodically with parameters Baptiste Mathus Do you have any update on this feature ? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56580) Configuration for JaCoCo plugin doesn't generate source inclusions
Title: Message Title
cristalp commented on JENKINS-56580
Re: Configuration for JaCoCo plugin doesn't generate source inclusions
Well, I can't see it on https://jenkinsci.github.io/job-dsl-plugin/#path/mavenJob-publishers-jacocoCodeCoverage When I try to use it with
jacocoCodeCoverage {
execPattern("**/${project}/**/target/**.exec")
inclusionPattern("**/*.class")
exclusionPattern("**/*Test*.class")
classPattern("**/${project}/**/target/classes")
sourcePattern("**/${project}/**/src/main/java")
sourceInclusionPattern('**/*.java')
}
I get
No signature of method: javaposse.jobdsl.dsl.helpers.publisher.JacocoContext.sourceInclusionPattern() is applicable for argument types: (java.lang.String) values: [**/*.java]
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56957) Jenkins Pipeline Parallel step console log format issue
Title: Message Title sakshi sood updated an issue Jenkins / JENKINS-56957 Jenkins Pipeline Parallel step console log format issue Change By: sakshi sood Labels: parallel 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39343) Persistent search/overviews/filtered views
Title: Message Title Ozgun Akalin commented on JENKINS-39343 Re: Persistent search/overviews/filtered views Any updates on this? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56957) Jenkins Pipeline Parallel step console log format issue
Title: Message Title sakshi sood updated an issue Jenkins / JENKINS-56957 Jenkins Pipeline Parallel step console log format issue Change By: sakshi sood We have recently upgraded jenkins to 2.150.3. Since the upgrade. the console logs of Jenkins parallel steps are less descriptive . It is not showing the parallel stage prefix anymore. It is very complicated to find out which stage on i am currently on. Is this expected ? Can this be configurable somewhere? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56957) Jenkins Pipeline Parallel step console log format issue
Title: Message Title sakshi sood created an issue Jenkins / JENKINS-56957 Jenkins Pipeline Parallel step console log format issue Issue Type: Improvement Assignee: Unassigned Attachments: earlier.JPG, now.JPG Components: workflow-job-plugin Created: 2019-04-10 12:35 Priority: Major Reporter: sakshi sood We have recently upgraded jenkins to 2.150.3. Since the upgrade. the console logs of Jenkins parallel steps are less descriptive . Is this expected ? Can this be configurable somewhere? Add Comment
[JIRA] (JENKINS-56874) Log4j2.xml file in the plugin causes unexpected errors
Title: Message Title Timothy Klopotoski commented on JENKINS-56874 Re: Log4j2.xml file in the plugin causes unexpected errors Looks to me like the userContent directory is writable by the user running the jenkins process. jenkins@my-docker-container ps PID USER TIME COMMAND 1 jenkins 0:02 /sbin/tini – /usr/local/bin/jenkins.sh 7 jenkins 51:43 java -Duser.home=/var/jenkins_home -Dhudson.model.DirectoryBrowserSupport.CSP= -Djenkins.install.runSetupWizard=false -Duser.timezone=America/New_York -jar /usr/share/jenkins/jenkins.war 8195 jenkins 0:00 /bin/bash 8204 jenkins 0:00 ps jenkins@my-docker-container whoami jenkins jenkins@my-docker-container ls -lah /var/jenkins_home/userContent/ total 8.0K drwxr-xr-x 2 jenkins jenkins 23 Apr 9 15:13 . drwx-- 20 jenkins jenkins 4.0K Apr 10 12:19 .. rw-rr- 1 jenkins jenkins 82 Apr 9 15:13 readme.txt 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34973) RejectedAccessException thrown but no pending script approval added
Title: Message Title William Will commented on JENKINS-34973 Re: RejectedAccessException thrown but no pending script approval added I will note that I was using a Jenkins pipeline and was having this issue when putting scripts in the Jenkins "failure" block, though not within a catch. It would seem that the "failure" block is implicitly a catch block. The workaround for me was running the script arbitrarily in one of the steps of the pipeline, so that it would come up in script approval, then moving it back to the failure block. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56956) Open Blue Ocean link with / character in branch name redirects to 404
Title: Message Title Mircea-Andrei Albu updated an issue Jenkins / JENKINS-56956 Open Blue Ocean link with / character in branch name redirects to 404 Change By: Mircea-Andrei Albu I am using a multi branch pipeline. The branches name contains a */*. Example: branch name is _feature/ABS-62317_When I am in a build in a multibranch pipeline in normal view, the URL is like this: job//job/feature%252FABS-62317//When I am pressing _Open Blue Ocean_ I am redirected to: blue/organizations/jenkins//detail/feature/ABS-62317// The problem is that this will result in 404, page not found. The correct link should've been blue/organizations/jenkins//detail/feature*%2F*ABS-62317//So replace the */* in the url of the branch name with *%2F* Finally, after replacing the text and seing the build pipeline in ocean blue mode, if I press next/previous(the arrows from top left) and then refresh, I am redirected again to the 404 page. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56956) Open Blue Ocean link with / character in branch name redirects to 404
Title: Message Title Mircea-Andrei Albu updated an issue Jenkins / JENKINS-56956 Open Blue Ocean link with / character in branch name redirects to 404 Change By: Mircea-Andrei Albu I am using a multi branch pipeline with having . The branches with name contains a */* in the name . Example: branch name is _feature/ABS-62317_When I am in a build in a multibranch pipeline in normal view, the URL is like this:job//job/feature%252FABS-62317//When I am pressing _Open Blue Ocean_ I am redirected to:blue/organizations/jenkins//detail/feature/ABS-62317//The problem is that this will result in 404, page not found.The correct link should've beenblue/organizations/jenkins//detail/feature*%2F*ABS-62317//So replace the */* in the url of the branch name with *%2F* 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56956) Open Blue Ocean link with / character in branch name redirects to 404
Title: Message Title Mircea-Andrei Albu created an issue Jenkins / JENKINS-56956 Open Blue Ocean link with / character in branch name redirects to 404 Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-04-10 10:56 Environment: Jenkins ver. 2.164.1, Blue Ocean 1.14.0 Labels: blueocean Priority: Minor Reporter: Mircea-Andrei Albu I am using a multi branch pipeline with having branches with / in the name. Example: branch name is feature/ABS-62317 When I am in a build in a multibranch pipeline in normal view, the URL is like this: job//job/feature%252FABS-62317// When I am pressing Open Blue Ocean I am redirected to: blue/organizations/jenkins//detail/feature/ABS-62317// The problem is that this will result in 404, page not found. The correct link should've been blue/organizations/jenkins//detail/feature*%2F*ABS-62317// So replace the / in the url of the branch name with %2F
[JIRA] (JENKINS-56723) Add unit tests for IssueDifference
Title: Message Title Artem Polovyi updated JENKINS-56723 Jenkins / JENKINS-56723 Add unit tests for IssueDifference Change By: Artem Polovyi Status: In Review Progress 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56723) Add unit tests for IssueDifference
Title: Message Title Artem Polovyi stopped work on JENKINS-56723 Change By: Artem Polovyi Status: In Progress Open 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56723) Add unit tests for IssueDifference
Title: Message Title Artem Polovyi started work on JENKINS-56723 Change By: Artem Polovyi Status: Open In Progress 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56723) Add unit tests for IssueDifference
Title: Message Title Artem Polovyi updated JENKINS-56723 Jenkins / JENKINS-56723 Add unit tests for IssueDifference Change By: Artem Polovyi Status: In Progress Review 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56251) Plugin Finds Files Only in Master Workspaces?
Title: Message Title mo xun resolved as Fixed Jenkins / JENKINS-56251 Plugin Finds Files Only in Master Workspaces? Change By: mo xun Status: In Progress Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/content-replace-plugin/releases/tag/content-replace-1.0.5 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title An Tran commented on JENKINS-55438 Re: Allow sequential stages inside parallel in Scripted syntax I found some tickets that maybe related: https://issues.jenkins-ci.org/browse/JENKINS-53751 https://issues.jenkins-ci.org/browse/JENKINS-53162 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56443) EC2 plugin doesn't take into account 'shutdown mode' of Jenkins
Title: Message Title Perrin Morrow commented on JENKINS-56443 Re: EC2 plugin doesn't take into account 'shutdown mode' of Jenkins I raised pull request #337 for this. It has already been merged. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43336) Allow locking multiple stages in declarative pipeline
Title: Message Title Andrii Vozniuk commented on JENKINS-43336 Re: Allow locking multiple stages in declarative pipeline Hi, just wanted to add that we have the same problem where we need to lock multiple stages at once for atomicity (environment build and integration tests go together). Also, we need to parametrise the lock with the environment against which the build is done: it is ok to have parallel builds against different environments, but not against the same one. As it looks, currently the multistage lock is available only in the options section which does not support environment parameters. Hence, it looks that we can not achieve what we need. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56955) Uninstalling Blueocean Plugin 1.4.0 plugin doesnt resolve dependency errors
Title: Message Title Carl Verbiest created an issue Jenkins / JENKINS-56955 Uninstalling Blueocean Plugin 1.4.0 plugin doesnt resolve dependency errors Issue Type: Bug Assignee: Unassigned Attachments: jenkins_systeminfo.txt Components: blueocean-plugin Created: 2019-04-10 08:55 Environment: jenkins.noarch 0:2.171-1.1 on Red Hat Enterprise Linux Server release 7.6 (Maipo) see attached jenkins_systeminfo.txt for systeminfo output Labels: configuration plugin-manager Priority: Minor Reporter: Carl Verbiest I'm experiencing the same issue as described in JENKINS-44935 but for version 1.4.0. The Blue Ocean UI has never started succesfully so I decided to remove it. I uninstalled all plugins containing blue. Errors shown on manage page. Dependency errors:Some plugins could not be loaded due to unsatisfied dependencies. Fix these issues and restart Jenkins to restore the functionality provided by these plugins.Config API for Blue Ocean version 1.14.0blueocean-commons version 1.14.0 is missing. To fix, install version 1.14.0 or later.Pipeline SCM API for Blue Ocean version 1.14.0blueocean-rest version 1.14.0 is missing. To fix, install version 1.14.0 or later.JWT for Blue Ocean
[JIRA] (JENKINS-56954) After upgrade to 2.164.1 from 2.150.3 injecting from file with absolute path does not work
Title: Message Title
Nikolaj Hestbek updated an issue
Jenkins / JENKINS-56954
After upgrade to 2.164.1 from 2.150.3 injecting from file with absolute path does not work
Change By:
Nikolaj Hestbek
We use ${TMP}\Jenkins\${BUILD_TAG}_inject.inp to point to a file in the "Inject environment variables" and "Parameters from properties file". Eg the path ${TMP} is absolute.This has always worked and the "Inject environment variables" still works. But after upgrading to Jenkins 2.164.1 "Parameters from properties file" reports an this error:[EnvInject] - Injecting environment variables from a build step.[EnvInject] - Injecting as environment variables the properties file path 'c:/temp/Jenkins/jenkins- CMArun Build Installer 1.6-82_inject.inp'[EnvInject] - Variables injected successfully.ERROR: Build step failed with exceptionjava.lang.IllegalArgumentException: Only a relative path is supported, the given path is absolute: c:/temp/Jenkins/jenkins -CMArun Build Installer 1.6-82_inject.inp/
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56954) After upgrade to 2.164.1 from 2.150.3 injecting from file with absolute path does not work
Title: Message Title
Nikolaj Hestbek created an issue
Jenkins / JENKINS-56954
After upgrade to 2.164.1 from 2.150.3 injecting from file with absolute path does not work
Issue Type:
Bug
Assignee:
Unassigned
Components:
parameterized-trigger-plugin
Created:
2019-04-10 07:56
Environment:
Jenkins 2.164.1 Google Chrome Job is run on slave
Priority:
Blocker
Reporter:
Nikolaj Hestbek
We use ${TMP}\Jenkins\${BUILD_TAG}_inject.inp to point to a file in the "Inject environment variables" and "Parameters from properties file". Eg the path ${TMP} is absolute. This has always worked and the "Inject environment variables" still works. But after upgrading to Jenkins 2.164.1 "Parameters from properties file" reports an this error: [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties file path 'c:/temp/Jenkins/jenkins-CMArun Build Installer 1.6-82_inject.inp' [EnvInject] - Variables injected successfully. ERROR: Build step failed with exception java.lang.IllegalArgumentException: Only a relative path is supported, the given path is absolute: c:/temp/Jenkins/jenkins-CMArun Build Installer 1.6-82_inject.inp/
[JIRA] (JENKINS-28119) Link to log of failed step
Title: Message Title Michael Hartmann commented on JENKINS-28119 Re: Link to log of failed step Is this still in progress? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56953) Surefire complains when std(out|err) is written to
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-56953 Surefire complains when std(out|err) is written to Issue Type: Task Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2019-04-10 06:59 Priority: Major Reporter: Oliver Gondža One of the causes is calling CommandBuilder#system() that redirects outs to INHERIT. Eliminate the use of the method in ATH. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56951) JIRA plugin config incorrectly mixed with properties section
Title: Message Title Francisco Fernández assigned an issue to Unassigned Jenkins / JENKINS-56951 JIRA plugin config incorrectly mixed with properties section Change By: Francisco Fernández Assignee: Francisco Fernández 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56951) JIRA plugin config incorrectly mixed with properties section
Title: Message Title Francisco Fernández updated an issue Jenkins / JENKINS-56951 JIRA plugin config incorrectly mixed with properties section Change By: Francisco Fernández Component/s: cloudbees-folder-plugin 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56952) Unable to load the service index for source https://api.nuget.org/v3/index.json.
Title: Message Title Girish Dubey updated an issue Jenkins / JENKINS-56952 Unable to load the service index for source https://api.nuget.org/v3/index.json. Change By: Girish Dubey *10:55:57* *10:55:57* C:\Builds\workspace\ci-job_master>"AutomatedProcedures\tools\nant-0.92\bin\nant.exe" -buildfile:AutomatedProcedures\NantScript.xml -D:Innovator.License.Type=Unlimited -D:Innovator.Activation.Key= D657E9F822F34433B8B58B62704129F9 -D:Innovator.License.Key= 3c1bdb569c74585842bd1bb4d6ad6490 3c1bdb569c74585xx -D:MSSQL.Innovator.Password= -D:MSSQL.Innovator.Regular.Password= -D:MSSQL.SA.Password= -D:MSSQL.Server=. -D:Path.To.CodeTree.Zip=F:\Project\CIPro\CodeTreeSP12.zip -D:Path.To.DB.Bak=F:\Project\CIPro\CoreAndSolutions110_SP12DB.bak -D:Branch.Name=master ContinuousIntegration *10:55:59* NAnt 0.92 (Build 0.92.4543.0; release; 09-06-2012)*10:55:59* Copyright (C) 2001-2012 Gerry Shaw*10:55:59* [http://nant.sourceforge.net|http://nant.sourceforge.net/]*10:55:59* *10:56:01* Buildfile: [file:///C:/Builds/workspace/ci-job_master/AutomatedProcedures/NantScript.xml]*10:56:01* Target framework: Microsoft .NET Framework 4.0*10:56:01* Target(s) specified: ContinuousIntegration *10:56:01* *10:56:03* [mkdir] Creating directory 'C:\Builds\workspace\ci-job_master\AutomatedProceduresOutput\TemporaryFilesAndLogs'.*10:56:03*[include] Including file C:\Builds\workspace\ci-job_master\AutomatedProcedures\Default.Settings.include.*10:56:03*[include] Including file C:\Builds\workspace\ci-job_master\AutomatedProcedures\Includes\NodeJs.include.*10:56:03*[include] Including file C:\Builds\workspace\ci-job_master\AutomatedProcedures\Includes\MSBuild.include.*10:56:03*[include] Including file C:\Builds\workspace\ci-job_master\AutomatedProcedures\Includes\ValidateEncoding.include.*10:56:03*[include] Including file C:\Builds\workspace\ci-job_master\AutomatedProcedures\Includes\EnvironmentDiagnostics.include.*10:56:04* [echo] SQL Server authentication will be used to access .*10:56:06* *10:56:06* Environment.Diagnostics:*10:56:06* *10:56:07* [echo] Version of node.js is v10.15.0*10:56:07* [echo] Version of C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe is 14.0*10:56:07* [echo] Windows version: Microsoft Windows [Version 10.0.17134.648]*10:56:07* *10:56:07* Initialize.Validate.Task:*10:56:07* *10:56:11* [exec] Feeds used:*10:56:11* [exec] [https://api.nuget.org/v3/index.json]*10:56:11* [exec] *10:56:23* [exec] Unable to load the service index for source [https://api.nuget.org/v3/index.json].*10:56:23* [exec] An error occurred while sending the request.*10:56:23* [exec] Unable to connect to the remote server*10:56:23* [exec] No connection could be made because the target machine actively refused it 127.0.0.1:5656*10:56:23* *10:56:23* BUILD FAILED - 0 non-fatal error(s), 4 warning(s)*10:56:23* *10:56:23* External Program Failed:
[JIRA] (JENKINS-36793) Need Support to queue when node is not a direct input parameter
Title: Message Title Satheesh Rajendran commented on JENKINS-36793 Re: Need Support to queue when node is not a direct input parameter Any progress/updates on this? Thanks in advance. 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. For more options, visit https://groups.google.com/d/optout.
