[JIRA] (JENKINS-52892) Jenkins On Jenkins: Clean up old branches
Title: Message Title Andrew Gray created an issue Jenkins / JENKINS-52892 Jenkins On Jenkins: Clean up old branches Issue Type: Task Assignee: Unassigned Components: jenkins-cloudformation Created: 2018-08-06 05:49 Priority: Minor Reporter: Andrew Gray Could someone please delete the old branches on the Jenkins on Jenkins instance. Are we every going to release from branch 2.89 ever again? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh edited a comment on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins [~cashlalala], Still I have validated the configurations comparing with yours, and now the build is not failing. Now I am facing issue as below, and the build is not ending and still it tried to run the 1st build job in the folder again and again, and it is not trying to execute the 2nd and next build jobs in the folder: Can you please try to trigger more than 1 job in a particular folder and update whether it is triggering all of them. Parameterized Remote Trigger Configuration: - job: // - remoteJenkinsName: Jenkins Server - parameters: [Version1=test22, Version2=test21] - blockBuildUntilComplete: false - connectionRetryLimit: 5fail to accquire lock because of timeout, skip locking...Triggering parameterized remote job 'http:///job/' Using globally defined 'Credentials Authentication' as user 'username' (Credentials ID 'my credentials id')Triggering remote job now.fail to accquire lock because of timeout, skip locking...CSRF protection is disabled on the remote server.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:34 min). Remote job queue number: 101142Waiting for remote build to be executed...Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:33 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:33 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:33 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:32 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:32 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:32 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:31 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking... Add Comment
[JIRA] (JENKINS-52865) Jenkins has error code 268435458.
Title: Message Title Oleg Nenashev commented on JENKINS-52865 Re: Jenkins has error code 268435458. Yes. But be sure that "C:\Program Files (x86)\Jenkins\jre\bin" contains a 32bit Java. If no, it would be a critical issue in the packaging. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins KaiHsiang Chang, Still I have validated the configurations comparing with yours, and now the build is not failing. Now I am facing issue as below, and the build is not ending and still it tried to run the 1st build job in the folder again and again, and it is not trying to execute the 2nd and next build jobs in the folder: Parameterized Remote Trigger Configuration: job: // remoteJenkinsName: Jenkins Server parameters: [Version1=test22, Version2=test21] blockBuildUntilComplete: false connectionRetryLimit: 5 fail to accquire lock because of timeout, skip locking... Triggering parameterized remote job 'http:///job/' Using globally defined 'Credentials Authentication' as user 'username' (Credentials ID 'my credentials id') Triggering remote job now. fail to accquire lock because of timeout, skip locking... CSRF protection is disabled on the remote server. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:34 min). Remote job queue number: 101142 Waiting for remote build to be executed... Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:33 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:33 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:33 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:32 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:32 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:32 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:31 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking...
[JIRA] (JENKINS-52741) have to supply all arguments when calling from pipeline
Title: Message Title Adrian Bridgett commented on JENKINS-52741 Re: have to supply all arguments when calling from pipeline Thanks for the info - we'll give it a go Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52886) when i try to access global configuring security option it throws an error while i can able to access all other options
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52886 when i try to access global configuring security option it throws an error while i can able to access all other options Change By: Oleg Nenashev Component/s: _unsorted Component/s: secure-requester-whitelist-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51936) Reduce trigger-happy building from master/upstream commits
Title: Message Title trejkaz commented on JENKINS-51936 Re: Reduce trigger-happy building from master/upstream commits After discussing this one with team members and others, I can confirm that we do still want to merge with the latest master if someone manually requests a new build, but that we still don't want new builds to kick off automatically for every change on master. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-46481) [BUILD_ID=dontKillMe] not work with PIPELINE BUILD's [sh] step
Title: Message Title Qin Ting closed an issue as Not A Defect Just a pipeline attribute problem. SEE https://wiki.jenkins.io/display/JENKINS/ProcessTreeKiller "In case of Jenkins Pipeline use JENKINS_NODE_COOKIE instead of BUILD_ID" can solve this problem perfectly. Jenkins / JENKINS-46481 [BUILD_ID=dontKillMe] not work with PIPELINE BUILD's [sh] step Change By: Qin Ting Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52592) After parent pom update, MessageOriginIdentityTest passes when run alone, fails when run with others
Title: Message Title Karl Shultz commented on JENKINS-52592 Re: After parent pom update, MessageOriginIdentityTest passes when run alone, fails when run with others Tom FENNELLY, if you could take a look at this, I'd really appreciate it. I suspect this is something you could figure out really quickly. I've got a fork/branch with the parent pom update already done, if you want to check that out. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52679) p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs
Title: Message Title Bharani Batna updated an issue Jenkins / JENKINS-52679 p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs Change By: Bharani Batna Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-42725) Active Choises Parameter - empty 'Classpath entry'
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-42725 Active Choises Parameter - empty 'Classpath entry' Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52592) After parent pom update, MessageOriginIdentityTest passes when run alone, fails when run with others
Title: Message Title Karl Shultz commented on JENKINS-52592 Re: After parent pom update, MessageOriginIdentityTest passes when run alone, fails when run with others Failures look like this: [ERROR] Failures: [ERROR] org.jenkinsci.plugins.pubsub.MessageOriginIdentityTest.test(org.jenkinsci.plugins.pubsub.MessageOriginIdentityTest) [ERROR] Run 1: MessageOriginIdentityTest.test:84 expected: but was: [ERROR] Run 2: MessageOriginIdentityTest.test:84 expected: but was: [ERROR] Run 3: MessageOriginIdentityTest.test:84 expected: but was: [ERROR] Run 4: MessageOriginIdentityTest.test:84 expected: but was: [ERROR] Run 5: MessageOriginIdentityTest.test:84 expected: but was: We're ending up here, it turns out. Jenkins is null when this test runs. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-40514) Typing Return Value of readMavenPom Causes ClassCastException
Title: Message Title Jesse Glick commented on JENKINS-40514 Re: Typing Return Value of readMavenPom Causes ClassCastException Filed a PR to formally deprecate these steps. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-49487) Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-49487 Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-40839) pipeline timeout doesn't kill the job
Title: Message Title Jesse Glick commented on JENKINS-40839 Re: pipeline timeout doesn't kill the job Maxfield Stewart While the sleep is running, put Jenkins in shutdown. Then cancel shutdown. is an unrelated known bug in workflow-cps-plugin. Zach Welz / plytro your cases are as designed. The timeout step throws an exception indicating that its body exceeded the timeout; you caught the exception and decided to proceed. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52678) Shared libraries stopped loading with git tags. The only now work when I reference a git branch name
Title: Message Title Mark Waite commented on JENKINS-52678 Re: Shared libraries stopped loading with git tags. The only now work when I reference a git branch name Did plugin versions change when you downgraded to 2.130 or when you upgraded to 2.133? In general, I would not expect a change of Jenkins version number to alter the specific behavior of the Pipeline code which loads library versions by tag or by branch name. There was a change in Git plugin 3.9.0 to restore the ability to load Pipeline shared libraries by SHA-1 in addition to loading them by branch name or tag. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51949) Docker agent in declarative pipeline failing to login to custom registry
Title: Message Title Jesse Glick commented on JENKINS-51949 Re: Docker agent in declarative pipeline failing to login to custom registry Daniel Fosbery not sure offhand. No developer of this plugin that I know of tests against AWS ECR. It may have specialized requirements for running docker login that go beyond what a generic registry does. If in doubt, avoid use of agent docker and run Docker commands directly from sh. Jarrett G any reason why what has not been updated yet? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52678) Shared libraries stopped loading with git tags. The only now work when I reference a git branch name
Title: Message Title Jon B commented on JENKINS-52678 Re: Shared libraries stopped loading with git tags. The only now work when I reference a git branch name Confirming that when we downgrade to 2.130, the original working behavior is restored. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52678) Shared libraries stopped loading with git tags. The only now work when I reference a git branch name
Title: Message Title Jon B commented on JENKINS-52678 Re: Shared libraries stopped loading with git tags. The only now work when I reference a git branch name Update: I have been able to determine that this problem emerges when I upgrade from Jenkins 2.130 to Jenkins 2.133 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52680) Migrating from DockerHub Jenkinsci to Jenkins/jenkins:lts images breaks while running the image
Title: Message Title
Pruthvi Raj Reddy Chukkannagari created an issue
Jenkins / JENKINS-52680
Migrating from DockerHub Jenkinsci to Jenkins/jenkins:lts images breaks while running the image
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
docker
Created:
2018-07-20 19:44
Priority:
Major
Reporter:
Pruthvi Raj Reddy Chukkannagari
As the jenkinsci docker hub was deprectaed I had to move to jenkins/jenkins:lts version of jenkins docker image which is of version 2.121.2. Earlier I was at 2.89.3. And now while I run the jenkins docker lts image with custom plugins using install_plugins.sh the image is being built but it fails to launch jenkins on container run with err:
// code placeholder
PORT0 is set to Running from: /usr/share/jenkins/jenkins.war webroot: EnvVars.masterEnvVars.get("JENKINS_HOME") Jul 20, 2018 7:41:19 PM org.eclipse.jetty.util.log.Log initialized INFO: Logging initialized @909ms to org.eclipse.jetty.util.log.JavaUtilLog Jul 20, 2018 7:41:20 PM winstone.Logger logInternal INFO: Beginning extraction from war file Jul 20, 2018 7:41:22 PM org.eclipse.jetty.server.handler.ContextHandler setContextPath WARNING: Empty contextPath Jul 20, 2018 7:41:22 PM winstone.Logger logInternal INFO: Jetty shutdown successfully java.io.IOException: Failed to start a listener: winstone.HttpConnectorFactory at winstone.Launcher.spawnListener(Launcher.java:209) at winstone.Launcher.(Launcher.java:148) at winstone.Launcher.main(Launcher.java:354) at
[JIRA] (JENKINS-52592) After parent pom update, MessageOriginIdentityTest passes when run alone, fails when run with others
Title: Message Title Karl Shultz assigned an issue to Tom FENNELLY Jenkins / JENKINS-52592 After parent pom update, MessageOriginIdentityTest passes when run alone, fails when run with others Change By: Karl Shultz Assignee: Karl Shultz Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-46089) ProcessTreeKiller broken in pipeline jobs
Title: Message Title Jesse Glick commented on JENKINS-46089 Re: ProcessTreeKiller broken in pipeline jobs Try sh ''' JENKINS_SERVER_COOKIE=ignore ./gradlew whatever ''' Maybe it works, maybe not, just a thought. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52249) Parallel build led to AIOOBE in Plot.savePlotData
Title: Message Title Jesse Glick commented on JENKINS-52249 Re: Parallel build led to AIOOBE in Plot.savePlotData Reinhold Füreder (a) yes, sure, which is why this is a bug in the plot plugin; (b) no, since this is a virtual machine using green threads, but there is a lock step. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-30148) Allocate shorter workspace if it will be too long for reasonable use inside build
Title: Message Title Jesse Glick commented on JENKINS-30148 Re: Allocate shorter workspace if it will be too long for reasonable use inside build Any change of having this fixed, ever Via my proposal in JENKINS-2111, perhaps. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52681) Anchore plugin fails with JSON error
Title: Message Title Ben Mathews created an issue Jenkins / JENKINS-52681 Anchore plugin fails with JSON error Issue Type: Bug Assignee: Daniel Nurmi Attachments: anchore.json, anchoreplugin.log, core.log Components: anchore-container-scanner-plugin Created: 2018-07-20 20:20 Environment: $ anchore-cli system status Service analyzer (61470748-b796-4901-aded-3a4ca537f8c8, N/A): up Service analyzer (c32c3eaf-399b-42d8-9b19-58a92aada103, N/A): up Service analyzer (f3926a02-e166-4698-9b5b-7849a29e47aa, N/A): up Service analyzer (1870d9d9-9ce0-44dd-b193-4d0ab064d018, N/A): up Service policy_engine (anchore_core_service, http://anchore-engine-anchore-engine:8087): up Service kubernetes_webhook (anchore_core_service, http://anchore-engine-anchore-engine:8338): up Service analyzer (a14c242a-206d-43a4-af61-f325dbdfe0d8, N/A): up Service catalog (anchore_core_service, http://anchore-engine-anchore-engine:8082): up Service apiext (anchore_core_service, http://anchore-engine-anchore-engine:8228): up Service simplequeue (anchore_core_service, http://anchore-engine-anchore-engine:8083): up Engine DB Version: 0.0.5 Engine Code Version: 0.1.10 Jenkins ver 2.125 Anchore plugin ver 1.0.16 Labels: plug-in jenkins plugins Priority: Major Reporter: Ben Mathews When I run a jenkins job using the anchore plugin, it submits it correctly but fails to load and parse
[JIRA] (JENKINS-40514) Typing Return Value of readMavenPom Causes ClassCastException
Title: Message Title Jesse Glick commented on JENKINS-40514 Re: Typing Return Value of readMavenPom Causes ClassCastException My advice remains to avoid these two steps. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-13174) Stop changeset tags from being counted as a change in Mercurial Plugin polling
Title: Message Title Jesse Glick commented on JENKINS-13174 Re: Stop changeset tags from being counted as a change in Mercurial Plugin polling Yes a Jenkins multibranch project. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-49365) Resuming of pipelines vs. docker.image(...).inside(...)?
Title: Message Title Jesse Glick commented on JENKINS-49365 Re: Resuming of pipelines vs. docker.image(...).inside(...)? I cannot speculate on the cause. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52680) Migrating from DockerHub Jenkinsci to Jenkins/jenkins:lts images breaks while running the image
Title: Message Title
Pruthvi Raj Reddy Chukkannagari updated an issue
Jenkins / JENKINS-52680
Migrating from DockerHub Jenkinsci to Jenkins/jenkins:lts images breaks while running the image
Change By:
Pruthvi Raj Reddy Chukkannagari
As the jenkinsci docker hub was deprectaed I had to move to jenkins/jenkins:lts version of jenkins docker image which is of version 2.121.2. Earlier I was at 2.89.3. And now while I run the jenkins docker jenkins: lts image with custom plugins using install_plugins.sh the image is being built but it fails to launch jenkins on container run with err:{code:java}// code placeholder{code}{code:java}PORT0 is set to Running from: /usr/share/jenkins/jenkins.war webroot: EnvVars.masterEnvVars.get("JENKINS_HOME") Jul 20, 2018 7:41:19 PM org.eclipse.jetty.util.log.Log initialized INFO: Logging initialized @909ms to org.eclipse.jetty.util.log.JavaUtilLog Jul 20, 2018 7:41:20 PM winstone.Logger logInternal INFO: Beginning extraction from war file Jul 20, 2018 7:41:22 PM org.eclipse.jetty.server.handler.ContextHandler setContextPath WARNING: Empty contextPath Jul 20, 2018 7:41:22 PM winstone.Logger logInternal INFO: Jetty shutdown successfully java.io.IOException: Failed to start a listener: winstone.HttpConnectorFactory at winstone.Launcher.spawnListener(Launcher.java:209) at winstone.Launcher.(Launcher.java:148) at winstone.Launcher.main(Launcher.java:354) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at Main._main(Main.java:312) at Main.main(Main.java:136) Caused by: java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:592) at java.lang.Integer.parseInt(Integer.java:615) at winstone.cmdline.Option.intArg(Option.java:294) at winstone.cmdline.Option$OInt.get(Option.java:206) at winstone.HttpConnectorFactory.start(HttpConnectorFactory.java:30) at winstone.Launcher.spawnListener(Launcher.java:207) ... 8 more Jul 20, 2018 7:41:22 PM winstone.Logger logInternal SEVERE: Container startup failed java.io.IOException: Failed to start a listener: winstone.HttpConnectorFactory at winstone.Launcher.spawnListener(Launcher.java:209) at winstone.Launcher.(Launcher.java:148) at winstone.Launcher.main(Launcher.java:354) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at Main._main(Main.java:312) at Main.main(Main.java:136) Caused by: java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at
[JIRA] (JENKINS-52682) Unable to read /var/lib/jenkins/config.xml
Title: Message Title Braunson Yager created an issue Jenkins / JENKINS-52682 Unable to read /var/lib/jenkins/config.xml Issue Type: Bug Assignee: Unassigned Attachments: config.xml Components: core Created: 2018-07-20 20:34 Environment: openjdk version "1.8.0_171" OpenJDK Runtime Environment (build 1.8.0_171-8u171-b11-0ubuntu0.16.04.1-b11) OpenJDK 64-Bit Server VM (build 25.171-b11, mixed mode) Running on Ubuntu 16.04.4 LTS Working Jenkins: 2.121.1 Not working Jenkins: 2.121.2 Labels: jenkins update Priority: Blocker Reporter: Braunson Yager Upgrading from 2.121.1 to 2.121.2 and it throws the error above. hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at hudson.WebAppMain$3.run(WebAppMain.java:244) Caused by: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:45) at jenkins.model.Jenkins.executeReactor(Jenkins.java:1010) at jenkins.model.Jenkins.(Jenkins.java:878) at
[JIRA] (JENKINS-52678) Shared libraries stopped loading with git tags. The only now work when I reference a git branch name
Title: Message Title
Jon B updated an issue
Jenkins / JENKINS-52678
Shared libraries stopped loading with git tags. The only now work when I reference a git branch name
Change By:
Jon B
I have a shared library in my Jenkins server that I call "common-pipelines". From within my Jenkinsfile, I will call for a specific *_tagged_* version of the common-pipelines shared library to be loaded like this:{code:java}@Library('common-pipelines@v9.4.4') _ {code}I was just alerted that the pipelines are erroring with the following message:{code:java}Please make sure you have the correct access rightsand the repository exists. {code}However, we aren't sure what changed. After much sanity checking, I was able to determine that this works normally if I call for a branch name rather than a github release (git tag).In other words, this works just fine:{code:java} @Library('common-pipelines@myBranchName') _ {code}I am running the latest plugins.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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-52678) Shared libraries stopped loading with git tags. The only now work when I reference a git branch name
Title: Message Title Jon B edited a comment on JENKINS-52678 Re: Shared libraries stopped loading with git tags. The only now work when I reference a git branch name [~markewaite] I am now running "Git plugin 3.9.0" with Jenkins 2.130 and things are working just fine. All of the evidence IMO suggests this breaks as a result of the upgrade to the jenkins core. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52678) Shared libraries stopped loading with git tags. The only now work when I reference a git branch name
Title: Message Title Jon B commented on JENKINS-52678 Re: Shared libraries stopped loading with git tags. The only now work when I reference a git branch name I am running "Git plugin 3.9.0" with Jenkins 2.130 and things are working just fine. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-20468) Multijob should provide configuration option to be a flyweight tasks
Title: Message Title Tim De Backer updated an issue Jenkins / JENKINS-20468 Multijob should provide configuration option to be a flyweight tasks Change By: Tim De Backer Comment: This would be very helpful indeed. We have a set-up in which only one job may run at the same time. We are combining this plugin with the NodeLabel Parameter plugin so all jobs of the MultiJob are run on the same node. However, the MultiJob itself takes up the single executor on that node! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-40839) pipeline timeout doesn't kill the job
Title: Message Title ilya s edited a comment on JENKINS-40839 Re: pipeline timeout doesn't kill the job Doesn't that basically defeat the purpose of this step? The expectation for users is that the timeout will kill whatever's in the timeout block. Effectively, this means that timeouts cannot be enforced by the pipeline when using libraries that aren don 't explicitly rethrow timeout exceptions. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-40839) pipeline timeout doesn't kill the job
Title: Message Title ilya s commented on JENKINS-40839 Re: pipeline timeout doesn't kill the job Doesn't that basically defeat the purpose of this step? The expectation for users is that the timeout will kill whatever's in the timeout block. Effectively, this means that timeouts cannot be enforced by the pipeline when using libraries that aren't explicitly rethrow timeout exceptions. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52678) Shared libraries stopped loading with git tags. The only now work when I reference a git branch name
Title: Message Title Jon B edited a comment on JENKINS-52678 Re: Shared libraries stopped loading with git tags. The only now work when I reference a git branch name [~markewaite] I am now running "Git plugin 3.9.0" with Jenkins 2.130 and things are working just fine. All of the evidence IMO suggests this breaks as a result of the upgrade to the newer jenkins core. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52678) Shared libraries stopped loading with git tags. The only now work when I reference a git branch name
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-52678 Shared libraries stopped loading with git tags. The only now work when I reference a git branch name Change By: Mark Waite Component/s: core Component/s: git-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52678) Shared libraries stopped loading with git tags. The only now work when I reference a git branch name
Title: Message Title Jon B edited a comment on JENKINS-52678 Re: Shared libraries stopped loading with git tags. The only now work when I reference a git branch name I am now running "Git plugin 3.9.0" with Jenkins 2.130 and things are working just fine. All of the evidence IMO suggests this breaks as a result of the upgrade to the jenkins core. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52678) Shared libraries stopped loading with git tags. The only now work when I reference a git branch name
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-52678 Shared libraries stopped loading with git tags. The only now work when I reference a git branch name Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52678) Shared libraries stopped loading with git tags. The only now work when I reference a git branch name
Title: Message Title Jon B edited a comment on JENKINS-52678 Re: Shared libraries stopped loading with git tags. The only now work when I reference a git branch name I am running "Git plugin 3.9.0" with Jenkins 2.130 and things are working just fine. All of the evidence IMO suggests this breaks as a result of the upgrade to the jenkins core. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-49622) Support Stride
Title: Message Title aldaris updated an issue Jenkins / JENKINS-49622 Support Stride Removing the hipchat-plugin component given that this plugin proposal has not much to do with HipChat (The APIs are quite different), and Atlassian is already in the process of creating a stride specific plugin already. Change By: aldaris Component/s: hipchat-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-16227) ProjectNamingStrategy: remove Default Strategy from the UI
Title: Message Title Guillaume Dupin edited a comment on JENKINS-16227 Re: ProjectNamingStrategy: remove Default Strategy from the UI Hi, I am currently having a weird behaviour concerning the "_Restrict project naming_" option and I think it is related to the current issue : * Initial state : the "_Restrict project naming_" checkbox is checked and a Strategy is chosen (let's take "Default" one for example) * I do not want to restrict naming so I uncheck the checkbox and save the configuration * I reload the page : the checkbox is checked again !?! Seems impossible to disable this optionIt is quite disturbing because in the UI, it seems possible to disable this option whereas I may understand with the current discussion that in reality the way to diable it is to choose "Default" strategy and the result is apparently the same. Is that right ?I know it has been some time since this ticket has been opened but would it be possible to look at it again please ?Environment : * Jenkins version : 2.121.1 * Role Strategy plugin version : 2.8.1 Update : after reading the code, it seems that this "_Restrict project naming_" checkbox component is currently an [optionalBlock|https://github.com/jenkinsci/jenkins/blob/d71ac6ffe98ee62e0353af7a948a4ae1a69b67e9/core/src/main/resources/jenkins/model/GlobalProjectNamingStrategyConfiguration/config.groovy#L7].Souldn't it be non-optional regarding to the real behaviour ? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52678) Shared libraries stopped loading with git tags. They only now work when I reference a git branch name
Title: Message Title Jon B updated an issue Jenkins / JENKINS-52678 Shared libraries stopped loading with git tags. They only now work when I reference a git branch name Change By: Jon B Summary: Shared libraries stopped loading with git tags. The They only now work when I reference a git branch name Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51531) Duplicate Code number of elements in table
Title: Message Title Ulli Hafner resolved as Won't Do Jenkins / JENKINS-51531 Duplicate Code number of elements in table Change By: Ulli Hafner Status: In Progress Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-30551) Make Warnings Plugin compatible with parallel Workflow
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-30551 Make Warnings Plugin compatible with parallel Workflow Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51437) Sidebar links should not show up for 0 issues
Title: Message Title Ulli Hafner started work on JENKINS-51437 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52526) Create a migrations generating container for evergreen deployment
Title: Message Title R. Tyler Croy updated JENKINS-52526 Jenkins / JENKINS-52526 Create a migrations generating container for evergreen deployment Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-48153) FindBugs does not trigger the build to fail on found issue
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-48153 FindBugs does not trigger the build to fail on found issue Change By: Ulli Hafner Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51910) Show reason for disabled health report
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-51910 Show reason for disabled health report Change By: Ulli Hafner Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-5597) symlinks in archive trees lead to double archiving
Title: Message Title E H updated an issue Jenkins / JENKINS-5597 symlinks in archive trees lead to double archiving Change By: E H Attachment: JENKINS-5597-example.groovy Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52681) Anchore plugin fails with JSON error
Title: Message Title Swathi Gangisetty commented on JENKINS-52681 Re: Anchore plugin fails with JSON error Ben Mathews, looks like your setup has the most updated Jenkins plugin release but a really old version of anchore engine (0.1.10). Current anchore engine release version is 0.2.3. This matters since the Jenkins plugin uses API to interact with anchore engine. "Security" tab of the Anchore build report is a new plugin feature that queries the anchore engine for vulnerabilities and renders the results. In this case the API response to vulnerability listing from the anchore engine is not what the plugin expects and hence the error in anchoreplugin.log. You might want to consider upgrading anchore engine for the Security tab results in the Anchore report. However, this error should not impact the rendering of the Anchore report for the Jenkins build. The Anchore report should display a "Policy" tab that contains a summary and detailed policy evaluation results. Let us know if this is not the case. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-5597) symlinks in archive trees lead to double archiving
Title: Message Title E H commented on JENKINS-5597 Re: symlinks in archive trees lead to double archiving Drawing on https://github.com/jenkinsci/pipeline-examples/blob/master/pipeline-examples/unstash-different-dir/unstashDifferentDir.groovy, the attached "JENKINS-5597-example.groovy" pipeline script will demonstrate the problem of symlinks to directories becoming directories. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52683) Allow flexible source definition in WorkflowBranchProjectFactories
Title: Message Title Steven Foster created an issue Jenkins / JENKINS-52683 Allow flexible source definition in WorkflowBranchProjectFactories Issue Type: New Feature Assignee: Stephen Connolly Components: branch-api-plugin, workflow-multibranch-plugin Created: 2018-07-20 22:51 Priority: Minor Reporter: Steven Foster I'd like to write an extension which allows a different script path to be set for Tag type heads. My use case is that my Branch type builds build, test and store artifacts ready for release/deploy. Only tag builds perform whatever is needed to release that artifact. Releasing can mean different things for different projects. For smaller projects, it's ok to have the entire pipeline run again with an additional release stage covered by a when directive checking for a tag. With a large project this is an unfortunate inefficiency. I would like to define a separate Jenkinsfile which just handles releasing the artifact previously built in the branch build. I figure this can be possible by defining a new BranchProjectFactory, and using the createDefinition method to pick one Jenkinsfile for branch/pr and one for tags. The method would need to expose information about the head being built though. Perhaps passing through the Branch object would be helpful?
[JIRA] (JENKINS-51497) Reference build not shown
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-51497 Reference build not shown Change By: Ulli Hafner Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-40839) pipeline timeout doesn't kill the job
Title: Message Title Jesse Glick commented on JENKINS-40839 Re: pipeline timeout doesn't kill the job The expectation for users is that the timeout will kill whatever's in the timeout block. Which it did. Whether or not the corresponding exception results in an immediate termination of the overall build with an ABORTED status is up to the script to decide. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-49059) Wrong option labels or help texts
Title: Message Title Ulli Hafner resolved as Fixed Obsolete. The new UI will use different elements. Jenkins / JENKINS-49059 Wrong option labels or help texts Change By: Ulli Hafner Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52499) All Descriptions throughout Jenkins, Change to AD_Login
Title: Message Title Travis Neal commented on JENKINS-52499 Re: All Descriptions throughout Jenkins, Change to AD_Login Update: I duplicated our entire Jenkins stack and started deleting things. Deleted every single plugin except the Amazon EC2 Plugin and all of its dependencies, deleted all files related to deleted plugins and deleted all builds and jobs from the server. It was still happening. However, I decided to delete all but 1 AMI profile in the configuration and it stopped updating the field to say "AD_Login". I then deleted 1 by 1, restarted the server and checked. It stopped after deleting the last windows profile. I then put them all back copying that section from the "live" jenkins server we have and pasting it in. It started happening again. Removed all the windows profiles and only the windows profiles, and it no longer updates the field to say "AD_Login". I don't feel like this is a way to fix it, but it's a way to get around it for now and at least SOME lead to go on when trying to debug this. I'm going to update the components on this ticket to show the ec2 plugin and hope that this ticket hasn't been lost to the abyss. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51910) Show reason for disabled health report
Title: Message Title Ulli Hafner started work on JENKINS-51910 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51437) Sidebar links should not show up for 0 issues
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-51437 Sidebar links should not show up for 0 issues Change By: Ulli Hafner Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52499) All Descriptions throughout Jenkins, Change to AD_Login
Title: Message Title Travis Neal assigned an issue to Francis Upton Jenkins / JENKINS-52499 All Descriptions throughout Jenkins, Change to AD_Login Change By: Travis Neal Component/s: ec2-plugin Component/s: credentials-plugin Assignee: Francis Upton Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-49912) Details Button should be available only if there are details
Title: Message Title Ulli Hafner resolved as Won't Do Every issue has a detail message Jenkins / JENKINS-49912 Details Button should be available only if there are details Change By: Ulli Hafner Status: In Progress Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-5597) symlinks in archive trees lead to double archiving
Title: Message Title E H edited a comment on JENKINS-5597 Re: symlinks in archive trees lead to double archiving Drawing on [https://github.com/jenkinsci/pipeline-examples/blob/master/pipeline-examples/unstash-different-dir/unstashDifferentDir.groovy,] the attached "JENKINS-5597-example.groovy" pipeline script will demonstrate the problem of symlinks to directories becoming directories. If the stash-related issue should be a different Jira issue please let me know and I'll create one. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-52684 Configuration Job-Watching in jobA affects all of other job's Job-Watching Change By: Rick Liu Attachment: Selection_007.png Attachment: Selection_008.png Attachment: Selection_009.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-46014) Specify parameters for build step
Title: Message Title Joshua Holmer commented on JENKINS-46014 Re: Specify parameters for build step This is huge for the company I'm at to be able to move to Blue Ocean for our deploys. I'd like to take on the work for this, if there are no objections. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-40839) pipeline timeout doesn't kill the job
Title: Message Title ilya s commented on JENKINS-40839 Re: pipeline timeout doesn't kill the job According to this example that's not accurate, since in the output we still get the second echo from within the timeout block. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-46014) Specify parameters for build step
Title: Message Title Joshua Holmer assigned an issue to Joshua Holmer Jenkins / JENKINS-46014 Specify parameters for build step Change By: Joshua Holmer Assignee: Joshua Holmer Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-16227) ProjectNamingStrategy: remove Default Strategy from the UI
Title: Message Title Guillaume Dupin edited a comment on JENKINS-16227 Re: ProjectNamingStrategy: remove Default Strategy from the UI Hi, I am currently having a weird behaviour concerning the "_Restrict project naming_" option and I think it is related to the current issue : * Initial state : the "_Restrict project naming_" checkbox is checked and a Strategy is chosen (let's take "Default" one for example) * I do not want to restrict naming so I uncheck the checkbox and save the configuration * I reload the page : the checkbox is checked again !?! Seems impossible to disable this optionIt is quite disturbing because in the UI, it seems possible to disable this option whereas I may understand with the current discussion that in reality the way to diable it is to choose "Default" strategy and the result is apparently the same. Is that right ?I know it has been some time since this ticket has been opened but would it be possible to look at it again please ?Environment : * Jenkins version : 2.121.1 * Role Strategy plugin version : 2.8.1 Update : after reading the code, it seems that this "_Restrict project naming_" checkbox component is currently an [ optionalBlock (cf. [here |https://github.com/jenkinsci/jenkins/blob/d71ac6ffe98ee62e0353af7a948a4ae1a69b67e9/core/src/main/resources/jenkins/model/GlobalProjectNamingStrategyConfiguration/config.groovy#L7].Souldn't it be non-optional regarding to the real behaviour ? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-16227) ProjectNamingStrategy: remove Default Strategy from the UI
Title: Message Title Guillaume Dupin edited a comment on JENKINS-16227 Re: ProjectNamingStrategy: remove Default Strategy from the UI Hi, I am currently having a weird behaviour concerning the "_Restrict project naming_" option and I think it is related to the current issue : * Initial state : the "_Restrict project naming_" checkbox is checked and a Strategy is chosen (let's take "Default" one for example) * I do not want to restrict naming so I uncheck the checkbox and save the configuration * I reload the page : the checkbox is checked again !?! Seems impossible to disable this optionIt is quite disturbing because in the UI, it seems possible to disable this option whereas I may understand with the current discussion that in reality the way to diable it is to choose "Default" strategy and the result is apparently the same. Is that right ?I know it has been some time since this ticket has been opened but would it be possible to look at it again please ?Environment : * Jenkins version : 2.121.1 * Role Strategy plugin version : 2.8.1 Update : after reading the code, it seems that this "_Restrict project naming_" checkbox component is currently an optionalBlock (cf. [here|https://github.com/jenkinsci/jenkins/blob/d71ac6ffe98ee62e0353af7a948a4ae1a69b67e9/core/src/main/resources/jenkins/model/GlobalProjectNamingStrategyConfiguration/config.groovy#L7] ) .Souldn't it be non-optional regarding to the real behaviour ? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-46014) Specify parameters for build step
Title: Message Title Joshua Holmer started work on JENKINS-46014 Change By: Joshua Holmer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-5597) symlinks in archive trees lead to double archiving
Title: Message Title E H commented on JENKINS-5597 Re: symlinks in archive trees lead to double archiving As well as being a a size issue, this breaks macOS Frameworks for code signing with a "bundle format is ambiguous (could be app or framework)" message. I found this with stash/unstash, presumably the cause is the same. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-52684 Configuration Job-Watching in jobA affects all of other job's Job-Watching Change By: Rick Liu Steps:1. Create 2 free-style jobs with "Watch Job" enabled: *Test1 and Test2*2. Click "*Watch Job*" link to configure job watching for *Test1* joband "*SUBMIT*" and the link becomes "*Configure Job Watching*"3. Open *Test2* job and "Watch Job" link becomes "*Configure Job Watching*" too!4. Under "*User > Configure > Extended Email Job Watching*" setcion,it shows "*No configuration available*"--At this point, only *Test1* watch job email notification is really working--5. Open *Test2* job and click " * Configure Job Watching * " and "*SUBMIT*"--Now both Test1 and Test2 watch job email notification is working.But job wtach configuration in one job affects configurations in other jobs,and "*User > Configure > Extended Email Job Watching*" setcion still shows "*No configuration available*".--6. Open "*Test1*" job and stop job watching.--This would stop all of job watching including "*Test2*"."*Test2*" job link becomes "*Watch Job*" and no more emails-- Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received
[JIRA] (JENKINS-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-52684 Configuration Job-Watching in jobA affects all of other job's Job-Watching Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2018-07-21 00:49 Environment: Ubuntu 16.04.4 OpenJDK 8u171-b11-0ubuntu0.16.04.1 Jenkins core 2.107.3 | 2.46.2 Email Extension 2.62 | 2.57.2 Priority: Critical Reporter: Rick Liu Steps: 1. Create 2 free-style jobs with "Watch Job" enabled: Test1 and Test2 2. Click "Watch Job" link to configure job watching for Test1 job and "SUBMIT" and the link becomes "Configure Job Watching" 3. Open Test2 job and "Watch Job" link becomes "Configure Job Watching" too! 4. Under "User > Configure > Extended Email Job Watching" setcion, it shows "No configuration available" -- At this point, only Test1 watch job email notification is really working -- 5. Open Test2 job and click "Configure Job Watching" and "SUBMIT" -- Now both Test1 and Test2 watch job email notification is working. But job wtach configuration in one job affects configurations in other jobs, and "User > Configure > Extended Email Job Watching" setcion still shows "No configuration available". -- 6. Open "Test1" job and stop job watching. -- This would stop all of job watching including "Test2". "Test2" job link becomes "Watch Job" and no more emails --
[JIRA] (JENKINS-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu commented on JENKINS-52684 Re: Configuration Job-Watching in jobA affects all of other job's Job-Watching I can reproduce on: Jenkins core 2.107.3 Email Extension 2.62 and Jenkins core 2.46.2 Email Extension 2.57.2 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52684) Configuration Job-Watching in jobA affects all of other job's Job-Watching
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-52684 Configuration Job-Watching in jobA affects all of other job's Job-Watching Change By: Rick Liu Steps:1. Create 2 free-style jobs with "Watch Job" enabled: *Test1 and Test2*2. Click "*Watch Job*" link to configure job watching for *Test1* joband "*SUBMIT*" and the link becomes "*Configure Job Watching*"3. Open *Test2* job and "Watch Job" link becomes " * Configure Job Watching * " too!4. Under "*User > Configure > Extended Email Job Watching*" setcion,it shows "*No configuration available*"--At this point, only *Test1* watch job email notification is really working--5. Open *Test2* job and click "Configure Job Watching" and "*SUBMIT*"--Now both Test1 and Test2 watch job email notification is working.But job wtach configuration in one job affects configurations in other jobs,and "*User > Configure > Extended Email Job Watching*" setcion still shows "*No configuration available*".--6. Open "*Test1*" job and stop job watching.--This would stop all of job watching including "*Test2*"."*Test2*" job link becomes "*Watch Job*" and no more emails-- Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received
[JIRA] (JENKINS-52698) 'Run could not start' error from HPE Application Automation Tools plugin
Title: Message Title Umesh Gachinmath commented on JENKINS-52698 Re: 'Run could not start' error from HPE Application Automation Tools plugin Continued from JENKINS-52366 : Daniel Danan. I had build new project from scratch, but still I got the same exception : Started by user Umesh S G Building in workspace C:\Program Files (x86)\Jenkins\workspace\PCTest Mon 07.23.2018 at 03:57:55 PM IST - plugin version is '5.4.3-beta-SNAPSHOT' Mon 07.23.2018 at 03:57:55 PM IST - - - Test description: PC Test Mon 07.23.2018 at 03:57:55 PM IST - Validating parameters before run Mon 07.23.2018 at 03:57:55 PM IST - OK Mon 07.23.2018 at 03:57:55 PM IST - Trying to login [PCServer=' http://http://awt-xxx-g-xxx02.fe.cosng.net/loadtest/General/Login.aspx?logout=1 ', User='e211158'] Mon 07.23.2018 at 03:57:58 PM IST - Login succeeded Mon 07.23.2018 at 03:57:58 PM IST - Searching for available Test Instance Mon 07.23.2018 at 03:57:59 PM IST - getCorrectTestInstanceID failed, reason: com.thoughtworks.xstream.mapper.CannotResolveClassException: htmlMon 07.23.2018 at 03:57:59 PM IST - java.lang.NumberFormatException: null Mon 07.23.2018 at 03:58:01 PM IST - Logout succeeded Mon 07.23.2018 at 03:58:01 PM IST - Empty Results Mon 07.23.2018 at 03:58:01 PM IST - Result Status: FAILURE - - Build step 'Execute performance test using Performance Center' changed build result to FAILURE Finished: FAILURE Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-48470) Unknown client name for JNLP4-connect
Title: Message Title Taehyun Kim updated an issue Jenkins / JENKINS-48470 Unknown client name for JNLP4-connect Change By: Taehyun Kim Comment: I'm having the same issue with jenkins 2.135kubernetes plugin 1.12 and 1.10.2 (I tried both version, but having the same problem) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52741) have to supply all arguments when calling from pipeline
Title: Message Title Kazuhide Takahashi commented on JENKINS-52741 Re: have to supply all arguments when calling from pipeline Unfortunately, since Xcode Integration Pliugin is written in an old Jenkins style, its compatibility with the Pipeline is very low. Currently we are working on releasing new versions that have improved this situation as soon as possible. You can get the pre-release version with the release planned improvement applied from the following URL, so please try this. https://ci.jenkins.io/job/Plugins/job/xcode-plugin/job/master/62/ Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-48470) Unknown client name for JNLP4-connect
Title: Message Title Taehyun Kim commented on JENKINS-48470 Re: Unknown client name for JNLP4-connect I'm having the same issue with jenkins 2.135 kubernetes plugin 1.12 and 1.10.2 (I tried both version, but having the same problem) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-50365) reload pipeline script without executing the job
Title: Message Title Jarrad Whitaker updated an issue Jenkins / JENKINS-50365 reload pipeline script without executing the job Change By: Jarrad Whitaker Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-50365) reload pipeline script without executing the job
Title: Message Title Jarrad Whitaker updated an issue Jenkins / JENKINS-50365 reload pipeline script without executing the job Change By: Jarrad Whitaker Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-50365) reload pipeline script without executing the job
Title: Message Title Jarrad Whitaker commented on JENKINS-50365 Re: reload pipeline script without executing the job Would the aspect that "parameters are in Jenkinsfile, but don't get used when I run the project" make this considered a bug? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52891) Always log the timeout for a CliGit command
Title: Message Title René Scheibe started work on JENKINS-52891 Change By: René Scheibe Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52891) Always log the timeout for a CliGit command
Title: Message Title René Scheibe assigned an issue to René Scheibe Jenkins / JENKINS-52891 Always log the timeout for a CliGit command Change By: René Scheibe Assignee: René Scheibe Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52891) Always log the timeout for a CliGit command
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-52891 Always log the timeout for a CliGit command Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52891) Always log the timeout for a CliGit command
Title: Message Title René Scheibe created an issue Jenkins / JENKINS-52891 Always log the timeout for a CliGit command Issue Type: Improvement Assignee: Mark Waite Components: git-client-plugin Created: 2018-08-05 18:12 Environment: git-client-3.0.0-beta5 Labels: git timeout logging Priority: Minor Reporter: René Scheibe A timeout is always used for a cli git command and therefore should always be logged. Options a timeout may be set timeout parameter for some commands system property org.jenkinsci.plugins.gitclient.Git.timeOut default of 10 minutes So far the timeout was only logged for commands where a) it cannot be customized b) it can and actually was customized Category a) some commands with correct default timeout logging so far > git --version # timeout=10 > git init ... # timeout=10 > git config ... # timeout=10 > git submodule init # timeout=10 Category b) commands with missing default timeout logging so far > git fetch ... > git checkout ... > git submodule update ...
[JIRA] (JENKINS-42840) Slave to Agent Renaming: SSH Slaves Plugin
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-42840 Slave to Agent Renaming: SSH Slaves Plugin Change By: Ivan Fernandez Calvo Assignee: Kohsuke Kawaguchi Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-42840) Slave to Agent Renaming: SSH Slaves Plugin
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-42840 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-42840) Slave to Agent Renaming: SSH Slaves Plugin
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-42840 Re: Slave to Agent Renaming: SSH Slaves Plugin Pending to change SSH Slaves Plugin to something else, these are the proposals: SSH Nodes Plugins SSH Agent Nodes Plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-46093) sshd zombie processes when using ssh slaves
Title: Message Title Ivan Fernandez Calvo closed an issue as Cannot Reproduce I cannot replicate it on 1.27-SNAPSHOT + Jenkins 2.73.3 Jenkins / JENKINS-46093 sshd zombie processes when using ssh slaves Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-42564) App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException)
Title: Message Title Mez Pahlan closed an issue as Won't Fix Appears to be an issue with how the path is specified by the end user. GLOB patterns aren't absolute but relative to the workspace. Jenkins / JENKINS-42564 App cannot be copy to Jenkins Master in HockeyApp 1.2.2 (Error: java.lang.NullPointerException) Change By: Mez Pahlan Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52881) durable-task plugin v1.23 kills jobs on Cygwin/MSys agents
Title: Message Title Andreas Engel commented on JENKINS-52881 Re: durable-task plugin v1.23 kills jobs on Cygwin/MSys agents As far as I understand it, for shell scripts, the durable task plugin starts a background process which regularly touches the mentioned log file. The failing "ps" command prevents this, so after HEARTBEAT_CHECK_INTERVAL seconds, the job gets killed. I initially tried to set it to 10 hours, i.e. 36000, which was sufficient for our current jobs, but seems to be a very crude workaround. Git on Windows is based on MSys btw. We use that too. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52641) Implemtation Hubot
Title: Message Title Naresh Rayapati commented on JENKINS-52641 Re: Implemtation Hubot Antonio Calderon Let me know if you were able to implement any of this, appreciate you inputs . Thank you. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52641) Implemtation Hubot
Title: Message Title
Naresh Rayapati commented on JENKINS-52641
Re: Implemtation Hubot
awesome! Antonio Calderon Maintaining the roles and approving job based on the user who is responded to that over slack would a bit hard part. That depends on how we manage hubot script which is actually making approval calls using standard creds (bot). https://github.com/jenkinsci/hubot-steps-plugin/blob/master/scripts/jenkins.coffee Another simple way is to maintain every job with an extra params for slack user and print, though the bot user made a approval call and it would send the user name along who responded from Slack/other services. (I haven't tried this but just an idea) # {msg.message.user.name} for user name and on https://github.com/jenkinsci/hubot-steps-plugin/blob/master/scripts/jenkins.coffee#L57
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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-52641) Implemtation Hubot
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-52641 Implemtation Hubot Change By: Naresh Rayapati Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52641) Implemtation Hubot
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-52641 Implemtation Hubot Change By: Naresh Rayapati Issue Type: Bug Task Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-22657) Unable To Upload To HockeyApp Through Proxy
Title: Message Title Mez Pahlan resolved as Fixed Fixed with PR42. Jenkins / JENKINS-22657 Unable To Upload To HockeyApp Through Proxy Change By: Mez Pahlan Status: Reopened Resolved Assignee: Oliver H Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52847) durable-task plugin v1.23 misbehaves on BusyBox agents
Title: Message Title John Forrest commented on JENKINS-52847 Re: durable-task plugin v1.23 misbehaves on BusyBox agents Note JENKINS-52887 where use of bash shell on windows-based machines no longer works. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52881) durable-task plugin v1.23 kills jobs on Cygwin/MSys agents
Title: Message Title John Forrest commented on JENKINS-52881 Re: durable-task plugin v1.23 kills jobs on Cygwin/MSys agents I'm seeing this too. Jenkins master is on centos7. Slave is running on a Windows Server 2016 but (among other things) I'm using the docker plugin which in turn using git shell. I do have downgraded the durable task plugin - I tried the suggestion of setting: -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=600 in /etc/sysconfig/jenkins, and it made no difference. My guess is that despite the message it is the error on the ps that is being reacted to. The alternative workaround for me would be to stop using the docker plugin. Originally, before I worked out how to use "sh" from Jenkins on a PC (ensure git is installed to C:\git and add C:\git\usr\bin to the windows path), I did have some code that tried to build on windows via bat - basically doing it all myself. I'd prefer not to have to - problem cases to handle etc etc. If this does not get fixed I probably will. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52879) Explore testcontainers for test automation
Title: Message Title Pham Vu Tuan updated JENKINS-52879 Jenkins / JENKINS-52879 Explore testcontainers for test automation Change By: Pham Vu Tuan Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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.
