[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title D Pasto edited a comment on JENKINS-43894 Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo Good call [~tario] ! It works! I assumed I could just use environment variables that I believe existed, but whether it doesn't really exist, or the plugin only sees a subset of environment variables, it correctly found the reference repo using an env defined in the node! It's not as clean as an automatically defined variable would be, but it looks like it works! We have a good sized repo so even though we're on-prem, I was seeing 2+ minute fetches for those stages where the hard-coded path was wrong, but this brings it down to 15 seconds in my first few runs Edit: forgot the most important part - this lets me define a single path (using forward slashes) that works on both Linux and Windows nodes. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181422.149329524.7396.1578942540367%40Atlassian.JIRA.
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title D Pasto commented on JENKINS-43894 Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo Good call Patrick Ruckstuhl Unable to render embedded object: File ( It works) not found. I assumed I could just use environment variables that I believe existed, but whether it doesn't really exist, or the plugin only sees a subset of environment variables, it correctly found the reference repo using an env defined in the node! It's not as clean as an automatically defined variable would be, but it looks like it works! We have a good sized repo so even though we're on-prem, I was seeing 2+ minute fetches for those stages where the hard-coded path was wrong, but this brings it down to 15 seconds in my first few runs Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181422.149329524.7385.1578942060314%40Atlassian.JIRA.
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title D Pasto commented on JENKINS-43894 Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo Any updates on releasing this? I verified it does not work on my v4.0 plugin (can resolve $JENKINS_HOME but not $HOME so is useless) and the changelog does not list it for that or v4.1 beta We have pipelines across many nodes, including different platforms, so we can't take full advantage of reference repos (the workaround of manually re-defining the checkout for every stage would be maintenance disaster) — we need a way of dynamically building the reference repo path per node per pipeline. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181422.149329524.7261.1578935340301%40Atlassian.JIRA.
[JIRA] (JENKINS-34545) Assigning roles is case sensitive, and it shouldn't be
Title: Message Title D Pasto commented on JENKINS-34545 Re: Assigning roles is case sensitive, and it shouldn't be I verified the workaround of assigning the user multiple times to each role: JoeUser, joeuser, Joeuser, JOEUSER It doesn't display right since the LDAP lookup doesn't like the duplication, and it wouldn't scale well, but it does work - I can login with the most common capitalization patterns and get the right permissions Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170162.1462223259000.9839.1565189100512%40Atlassian.JIRA.
[JIRA] (JENKINS-53332) Allow picking a lockable resource from a node label
Title: Message Title D Pasto commented on JENKINS-53332 Re: Allow picking a lockable resource from a node label JENKINS-44141 is talking about more complex data than the simple one to many relationship whereas this is integration with node labels/resources. There is nothing in that ticket that covers this, and they are not necessarily related but certainly could be implemented together. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193414.1535570763000.8053.1565024760458%40Atlassian.JIRA.
[JIRA] (JENKINS-55486) If lock() creates a new resource, there should be a choice to make it temporary
Title: Message Title D Pasto commented on JENKINS-55486 Re: If lock() creates a new resource, there should be a choice to make it temporary Fantastic, thanks! Unfortunately I don't have a sandbox to try pre-release versions. I see the last release of this plugin was in March, so I'll keep an eye out for it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196616.1547046002000.8017.1565021220374%40Atlassian.JIRA.
[JIRA] (JENKINS-55485) Declarative pipeline, lock() in stage options is executed before when clause
Title: Message Title D Pasto commented on JENKINS-55485 Re: Declarative pipeline, lock() in stage options is executed before when clause Yes, this duplicates: JENKINS-51865 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196615.1547045335000.8002.1565018940293%40Atlassian.JIRA.
[JIRA] (JENKINS-51865) Stage locks are created for skipped stages in declarative pipeline
Title: Message Title D Pasto commented on JENKINS-51865 Re: Stage locks are created for skipped stages in declarative pipeline It also doesn’t work because either you hardcore “dummy” and potentially block on it or you randomize and create all sorts of crap in your Jenkins config 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-50045) Pipeline showing multiple stages on failure
Title: Message Title D Pasto commented on JENKINS-50045 Re: Pipeline showing multiple stages on failure This can be really annoying - now you lose out on the benefit of the visualization making it immediately clear where the problem lies and how far the pipeline got. 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-55257) Timestamper break builds on Windows agents
Title: Message Title D Pasto edited a comment on JENKINS-55257 Re: Timestamper break builds on Windows agents Verified that upgrading the agent worked for me .We ran into this because we deployed agents from a VM template with an old jar, and Jenkins disabled automatic agent updates because we are not running HTTPS. 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-55257) Timestamper break builds on Windows agents
Title: Message Title D Pasto commented on JENKINS-55257 Re: Timestamper break builds on Windows agents Verified that upgrading the agent worked for me 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-55257) Timestamper break builds on Windows agents
Title: Message Title D Pasto commented on JENKINS-55257 Re: Timestamper break builds on Windows agents Looks similar to JENKINS-54058,[ as does the current characterization of this issue. What do you think? 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-55485) Declarative pipeline, lock() in stage options is executed before when clause
Title: Message Title D Pasto commented on JENKINS-55485 Re: Declarative pipeline, lock() in stage options is executed before when clause I verified the workaround of adding an additional level of stage - I have a group stage with the when clause containing a group stage with the lock, containing the actual stages. With this structure I'm able to use the when clause to disable deploy and test stages, and not get stuck waiting for a lock behind a long-running test. The workaround is conceptually easy, but adds a lot of boilerplate and makes the Jenkinsfile that much harder to read. I'm now up to 10 levels of tabs in my Jenkinsfile and have a check-in with hundreds of lines of changes that is just indenting. It's getting pretty ugly. This is exactly the mess the "beforeAgent" directive to the "when" clause prevents - we need a similar solution here. 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-37152) Support Win32-OpenSSH
Title: Message Title D Pasto commented on JENKINS-37152 Re: Support Win32-OpenSSH Any updates on how this went, or whether you're planning to pursue releasing this? Can it execute things requiring interaction with the desktop, such as Selenium tests? Is it not ready for prime time? Is Windows OpenSSH just not ready yet? 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-55257) Timestamper break builds on Windows agents
Title: Message Title D Pasto commented on JENKINS-55257 Re: Timestamper break builds on Windows agents Does this mean anything? Result: [file:/C:/Jenkins/slave.jar, null] 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-55257) Timestamper break builds on Windows agents
Title: Message Title D Pasto commented on JENKINS-55257 Re: Timestamper break builds on Windows agents > Channel.executor is public and should be in the same JAR file. What about the other direction? I’m not very familiar with jar files but they’re just zip files, right? Is there anything we can inspect? What file is this and what version? What can we try updating or reverting? 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-55486) If lock() creates a new resource, there should be a choice to make it temporary
Title: Message Title D Pasto commented on JENKINS-55486 Re: If lock() creates a new resource, there should be a choice to make it temporary I can see several ways of addressing this issue - this ticket is a small improvement that will get us a nice improvement, while JENKINS-53332 addresses the scenario, and JENKINS-44141 is a larger goal but is short on detail 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-55485) Declarative pipeline, lock() in stage options is executed before when clause
Title: Message Title
D Pasto updated an issue
Jenkins / JENKINS-55485
Declarative pipeline, lock() in stage options is executed before when clause
Change By:
D Pasto
In a a declarative pipeline i have a stage grouping several other stages and need to hold a lock for the duration of the group. I see I can add lock() to the options of the group and it works fine in that scenario. However the group also has a When clause so I can turn that group off with a job parameter. The problem is that when the "when" evaluates false so the stage will be skipped, it wait for the lock anyway. If the stage will be skipped for any reason, we should not block on the lock. The "when" defines a "beforeAgent" attribute for a similar need, so that might be an approach, but I'm not seeing a scenario where you would want to do it in the current order. My pipeline looks like: --- — pipeline {agent none stages { stage ('Build') { { } stage('Deploy-and-Test') { // Group Stage Deploy and test the Build - lock the deployment VM so we don't step on other runs when { _expression_ { "${params.Deploy}" == "true" } beforeAgent true } options { lock(quantity: 1, resource: "${params.DeployAgent}", variable: 'myDeployAgent') } agent none stages \{ ...} }}} When I run it withthe param to disable the stage I see: --- — [Pipeline] stage[Pipeline] { (Deploy-and-Test)[Pipeline] lockTrying to acquire lock on [DeploymentVM_Win]Lock acquired on [DeploymentVM_Win][Pipeline] {Stage "Deploy-and-Test" skipped due to when conditional --- — Since the stage is being skipped there is no point in holding the lock, but it the lock is already allocated, this will block anyway. The lock() should be processed _after_ the decision whether to execute the stage.
Add Comment
[JIRA] (JENKINS-55485) Declarative pipeline, lock() in stage options is executed before when clause
Title: Message Title D Pasto updated an issue Jenkins / JENKINS-55485 Declarative pipeline, lock() in stage options is executed before when clause Change By: D Pasto Summary: Declarative pipeline, lock() in stage aoptions options is executed before when clause 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-55486) If lock() creates a new resource, there should be a choice to make it temporary
Title: Message Title D Pasto created an issue Jenkins / JENKINS-55486 If lock() creates a new resource, there should be a choice to make it temporary Issue Type: Improvement Assignee: Unassigned Components: lockable-resources-plugin Created: 2019-01-09 15:00 Priority: Minor Reporter: D Pasto I'm using lock() in the stage options of a declarative pipeline and really like the feature to automatically create the resource if it does not yet exist. That should save some maintenance. However as time goes on and resources change, this means the number of resources builds up until someone cleans them out. We should have a choice for manually created locks to be temporary - i don't necessarily care whether the resource exists when no one is using it, just that only one job use it at a time. May be related to: JENKINS-34892 The overall scenario is related to Jenkins agents - I want a stage to deploy a server, followed by stages to execute client tests, but I need the server locked the whole time so that no other job tries to use it. Currently I'm stuck with double maintenance, keeping the same server list in both the agent and the lockable resources. If lock() both lets me create resources on the fly and declare them temporary so they are deleted when no one is using them, then I don't need duplicate maintenance - I only need to maintain the agents, not the lock data.
[JIRA] (JENKINS-55485) Declarative pipeline, lock() in stage aoptions is executed before when clause
Title: Message Title
D Pasto created an issue
Jenkins / JENKINS-55485
Declarative pipeline, lock() in stage aoptions is executed before when clause
Issue Type:
Bug
Assignee:
Unassigned
Components:
lockable-resources-plugin
Created:
2019-01-09 14:48
Priority:
Minor
Reporter:
D Pasto
In a a declarative pipeline i have a stage grouping several other stages and need to hold a lock for the duration of the group. I see I can add lock() to the options of the group and it works fine in that scenario. However the group also has a When clause so I can turn that group off with a job parameter. The problem is that when the "when" evaluates false so the stage will be skipped, it wait for the lock anyway. If the stage will be skipped for any reason, we should not block on the lock. My pipeline looks like: — pipeline { agent none stages { stage ('Build') { } stage('Deploy-and-Test') { // Group Stage Deploy and test the Build - lock the deployment VM so we don't step on other runs when { _expression_ { "${params.Deploy}" == "true" } beforeAgent true } options { lock(quantity: 1, resource: "${params.DeployAgent}", variable: 'myDeployAgent') } agent none stages { ...} }}} When I run it withthe param to disable the stage I see: — [Pipeline] stage[Pipeline] { (Deploy-and-Test)[Pipeline] lockTrying to acquire lock on [DeploymentVM_Win] Lock acquired on [DeploymentVM_Win][Pipeline] {Stage "Deploy-and-Test" skipped due to when conditional — Since the stage is being skipped there is no point in holding the lock, but it the lock is already allocated, this will block anyway. The lock() should be processed after the decision whether to execute the stage.
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title D Pasto edited a comment on JENKINS-55257 Re: Timestamper break builds on Windows agents For me this is happening on a Win 2012r2 agent, so it is not just Win2016. The Jenkins agent is running as administrator , I don't know of any with UAC or other privs changes, but I didn't deploy the servers set to never . 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-55257) Timestamper break builds on Windows agents
Title: Message Title D Pasto commented on JENKINS-55257 Re: Timestamper break builds on Windows agents For me this is happening on a Win 2012r2 agent, so it is not just Win2016. The Jenkins agent is running as administrator, I don't know of any UAC or other privs changes, but I didn't deploy the servers. 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-55257) Timestamper break builds on Windows agents
Title: Message Title D Pasto commented on JENKINS-55257 Re: Timestamper break builds on Windows agents FWIW - I'm running into what looks like the same issue. I have a declarative pipeline and couldn't understand why it's only my branch blowing up this way, and I see it with the default checkout, an explicit 'checkout scm', or 'git ...'. I'm running timestamper 1.8.10 and java 1.8.0_191-b12 64bit. Commenting out the timestamps option got me past 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-53332) Allow picking a lockable resource from a node label
Title: Message Title
D Pasto created an issue
Jenkins / JENKINS-53332
Allow picking a lockable resource from a node label
Issue Type:
Improvement
Assignee:
Unassigned
Components:
lockable-resources-plugin
Created:
2018-08-29 19:26
Priority:
Minor
Reporter:
D Pasto
This plugin has really helped in the scenario of testing client-server, or cloud applications where we want to lock a deployment across multiple test jobs, however we end up duplicating configuration between lockable resources and node. A really useful improvement to lockable resources would be to choose the resource from online nodes in a pool represented by a node label. For example, I currently configure:
node label "BACKEND_POOL" representing a pool of Jenkins nodes where I can deploy my applcation back end/services
lockable resources "SERVICE_POOL" with the identical list
Now I have a pipeline like pseudocode:
stage("Build") {
build()
}
RESOURCE = get lockable resource from SERVICE_POOL
stage ("Deploy") {
node (RESOURCE) {
deploy()
}
stage ("Test1") {
node ("Test") {
Test1(server=RESOURCE)
}
}
stage ("Test2") {
node ("Test") {
Test2 (server=RESOURCE)
}
}
However, now I am maintaining the same list of resources in both the node label/pool and the lockable resource pool. This leads to issues like nodes being locked for deployment even though they are offline, someone adding or deleting a resource from one pool but not the
[JIRA] (JENKINS-14545) Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname
Title: Message Title D Pasto edited a comment on JENKINS-14545 Re: Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname I see this is ancient at this point so i won't re-open , but the fix appears to have caused JENKINS-34340 . We need a more targetted fix for this Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14545) Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname
Title: Message Title D Pasto commented on JENKINS-14545 Re: Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname I see this is ancient at this point, but the fix appears to have caused JENKINS-34340 . We need a more targetted fix for this Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34340) Don't rename job names in TRIGGERED_JOB_NAMES
Title: Message Title D Pasto edited a comment on JENKINS-34340 Re: Don't rename job names in TRIGGERED_JOB_NAMES This also conflicts with jobs using the Cloudbees Folders plugin. For example, I am using this plugin to trigger a job in another folder. I expect to be able to use $LAST_TRIGGERED_JOB_NAME in the following copyArtifacts plugin to collect artifacts, but this replaces all '/' with underscore, so fails. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34340) Don't rename job names in TRIGGERED_JOB_NAMES
Title: Message Title D Pasto commented on JENKINS-34340 Re: Don't rename job names in TRIGGERED_JOB_NAMES This issue was caused by the resolution for JENKINS-14545, but we need a fix that will work in both cases. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34340) Don't rename job names in TRIGGERED_JOB_NAMES
Title: Message Title D Pasto commented on JENKINS-34340 Re: Don't rename job names in TRIGGERED_JOB_NAMES This also conflicts with jobs using the Folders plugin. For example, I am using this plugin to trigger a job in another folder. I expect to be able to use $LAST_TRIGGERED_JOB_NAME in the following copyArtifacts plugin to collect artifacts, but this replaces all '/' with underscore, so fails. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41005) Violations plugin makes concurrent builds wait
Title: Message Title D P commented on JENKINS-41005 Re: Violations plugin makes concurrent builds wait This looks like the meta-bug JENKINS-9913 collecting bad plugin behavior. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41005) Violations plugin makes concurrent builds wait
Title: Message Title D P updated an issue Jenkins / JENKINS-41005 Violations plugin makes concurrent builds wait Change By: D P I have several jobs executing concurrently against a pool of machines using a node label. However, each is not able to finish, but has to wait for all concurrent jobs, during the post-build step to report violations.Console output from the job is stuck at:- Report Violations is waiting for a checkpoint on Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41005) Violations plugin makes concurrent builds wait
Title: Message Title D P created an issue Jenkins / JENKINS-41005 Violations plugin makes concurrent builds wait Issue Type: Bug Assignee: Tomas Bjerre Components: violations-plugin Created: 2017/Jan/11 10:14 PM Priority: Minor Reporter: D P Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-40125) Terraform plugin does not work with Jenkins v2.19
Title: Message Title D P edited a comment on JENKINS-40125 Re: Terraform plugin does not work with Jenkins v2.19 [11/30/2016 11:26 AM] Jeffrey Tompkins: Java(TM) SE Runtime Environment (build 1.7.0_67-b01) Nov 30, 2016 9:39:03 AM hudson.ExtensionFinder$Sezpoz scoutWARNING: Failed to scout org.jenkinsci.plugins.terraform.TerraformBuildWrapper$DescriptorImpljava.lang.InstantiationException: java.lang.UnsupportedClassVersionError: org/jenkinsci/plugins/terraform/TerraformBuildWrapper$DescriptorImpl : Unsupported major.minor version 52.0 at net.java.sezpoz.IndexItem.element(IndexItem.java:146) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:656) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:472) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.getComponents(ExtensionList.java:167) at jenkins.model.Jenkins$8.onInitMilestoneAttained(Jenkins.java:1069) at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:82) at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:104) at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:176) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.UnsupportedClassVersionError: org/jenkinsci/plugins/terraform/TerraformBuildWrapper$DescriptorImpl : Unsupported major.minor version 52.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1139) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:885) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1310) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1363) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44) at jenkins.ClassLoaderReflectionToolkit._findClass(ClassLoaderReflectionToolkit.java:81) at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:1851) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) ... 13 more Add Comment
[JIRA] (JENKINS-40125) Terraform plugin does not work with Jenkins v2.19
Title: Message Title D P edited a comment on JENKINS-40125 Re: Terraform plugin does not work with Jenkins v2.19 [11/30/2016 11:26 AM] Jeffrey Tompkins: Java(TM) SE Runtime Environment (build 1.7.0_67-b01) Nov 30, 2016 9:39:03 AM hudson.ExtensionFinder$Sezpoz scoutWARNING: Failed to scout org.jenkinsci.plugins.terraform.TerraformBuildWrapper$DescriptorImpljava.lang.InstantiationException: java.lang.UnsupportedClassVersionError: org/jenkinsci/plugins/terraform/TerraformBuildWrapper$DescriptorImpl : Unsupported major.minor version 52.0 at net.java.sezpoz.IndexItem.element(IndexItem.java:146) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:656) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:472) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.getComponents(ExtensionList.java:167) at jenkins.model.Jenkins$8.onInitMilestoneAttained(Jenkins.java:1069) at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:82) at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:104) at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:176) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.UnsupportedClassVersionError: org/jenkinsci/plugins/terraform/TerraformBuildWrapper$DescriptorImpl : Unsupported major.minor version 52.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1139) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:885) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1310) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1363) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44) at jenkins.ClassLoaderReflectionToolkit._findClass(ClassLoaderReflectionToolkit.java:81) at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:1851) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) ... 13 more Add Comment
[JIRA] (JENKINS-40125) Terraform plugin does not work with Jenkins v2.19
Title: Message Title D P commented on JENKINS-40125 Re: Terraform plugin does not work with Jenkins v2.19 Nov 30, 2016 9:39:03 AM hudson.ExtensionFinder$Sezpoz scout WARNING: Failed to scout org.jenkinsci.plugins.terraform.TerraformBuildWrapper$DescriptorImpl java.lang.InstantiationException: java.lang.UnsupportedClassVersionError: org/jenkinsci/plugins/terraform/TerraformBuildWrapper$DescriptorImpl : Unsupported major.minor version 52.0 at net.java.sezpoz.IndexItem.element(IndexItem.java:146) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:656) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:472) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.getComponents(ExtensionList.java:167) at jenkins.model.Jenkins$8.onInitMilestoneAttained(Jenkins.java:1069) at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:82) at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:104) at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:176) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.UnsupportedClassVersionError: org/jenkinsci/plugins/terraform/TerraformBuildWrapper$DescriptorImpl : Unsupported major.minor version 52.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1139) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:885) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1310) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1363) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44) at jenkins.ClassLoaderReflectionToolkit._findClass(ClassLoaderReflectionToolkit.java:81) at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:1851) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) ... 13 more Add Comment
[JIRA] (JENKINS-40125) Terraform plugin does not work with Jenkins v2.19
Title: Message Title D P updated an issue Jenkins / JENKINS-40125 Terraform plugin does not work with Jenkins v2.19 Change By: D P Environment: Jenkins ver. 2.19.2 LTS on CentOS Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40125) Terraform plugin does not work with Jenkins v2.19
Title: Message Title D P edited a comment on JENKINS-40125 Re: Terraform plugin does not work with Jenkins v2.19 I am aware there is a pull request in progress that may be related : https://github.com/jenkinsci/terraform-plugin/pull/2 however there are no symptoms described there. I don't think I can help move it along but can at least raise the visibility of the issue . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40125) Terraform plugin does not work with Jenkins v2.19
Title: Message Title D P updated an issue Jenkins / JENKINS-40125 Terraform plugin does not work with Jenkins v2.19 Change By: D P Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40125) Terraform plugin does not work with Jenkins v2.19
Title: Message Title D P commented on JENKINS-40125 Re: Terraform plugin does not work with Jenkins v2.19 I am aware there is a pull request in progress: https://github.com/jenkinsci/terraform-plugin/pull/2 I don't think I can help move it along but can at least raise the visibility of the issue Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40125) Terraform plugin does not work with Jenkins v2.19
Title: Message Title D P created an issue Jenkins / JENKINS-40125 Terraform plugin does not work with Jenkins v2.19 Issue Type: Bug Assignee: David Pires Components: terraform-plugin Created: 2016/Nov/30 3:51 PM Environment: Jenkins ver. 2.19.2 on CentOS Priority: Minor Reporter: D P I installed the Terraform plugin without any apparent error, however no changes show up either in the system config or job config Add Comment
[JIRA] (JENKINS-39384) Multi-job phase should stop when sub-job is disabled
Title: Message Title D P created an issue Jenkins / JENKINS-39384 Multi-job phase should stop when sub-job is disabled Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 2016/Oct/31 2:00 PM Environment: Jenkins 1.651.3 mulit-job plugin 1.23 Priority: Minor Reporter: D P I have a build chain configured as a multi-job, however I want to stop it early so the job in the third phase, "Deploy", is temporarily disabled. That phase is configured to continue to next phase when jobs' statuses are 'Successfull'. (doesn't make sense to verify the deployed product if we're not deploying) The job can not succeed since it is disabled but the phase completes and the next phase runs anyway. This should be fixed so that successful means successful, or add another option to continue only when successfull. Add Comment
[JIRA] (JENKINS-38832) Add SSH Slaves support for tracking credentials usage
Title: Message Title D P created an issue Jenkins / JENKINS-38832 Add SSH Slaves support for tracking credentials usage Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: ssh-slaves-plugin Created: 2016/Oct/07 8:35 PM Priority: Minor Reporter: D P The credentials plug-in added support for tracking credentials usage, see JENKINS-20139. However the consumer plug-in needs an update to enable this. Please add support. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-38831) Add Credentials Binding support for tracking credentials usage
Title: Message Title D P created an issue Jenkins / JENKINS-38831 Add Credentials Binding support for tracking credentials usage Issue Type: Improvement Assignee: Unassigned Components: credentials-binding-plugin Created: 2016/Oct/07 8:26 PM Priority: Minor Reporter: D P The credentials plug-in added support for tracking credentials usage, see JENKINS-20139. However the consumer plug-in needs an update to enable this. Please add support. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-38830) Add SSH Agent support for tracking credential usage
Title: Message Title D P created an issue Jenkins / JENKINS-38830 Add SSH Agent support for tracking credential usage Issue Type: Improvement Assignee: Unassigned Components: ssh-agent-plugin Created: 2016/Oct/07 8:21 PM Priority: Minor Reporter: D P The credentials plug-in added support for tracking credentials usage, see JENKINS-20139. However the consumer plug-in needs an update to enable this. Please add support. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-38828) Add pull request builder support for tracking credential usage
Title: Message Title D P created an issue Jenkins / JENKINS-38828 Add pull request builder support for tracking credential usage Issue Type: Improvement Assignee: ben patterson Components: ghprb-plugin Created: 2016/Oct/07 8:16 PM Priority: Minor Reporter: D P The credentials plug-in added support for tracking credentials usage, see JENKINS-20139. However the consumer plug-in needs an update to enable this. Please add support. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-38827) Add Git Client support to track where a credential is used
Title: Message Title D P created an issue Jenkins / JENKINS-38827 Add Git Client support to track where a credential is used Issue Type: Improvement Assignee: Mark Waite Components: git-client-plugin Created: 2016/Oct/07 8:01 PM Priority: Minor Reporter: D P The credentials plug-in added support for tracking credentials usage, see JENKINS-20139. However the consumer plug-in needs an update to enable this. Please add support. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-38826) Add SSH Credential support to track where a credential is used
Title: Message Title D P updated an issue Jenkins / JENKINS-38826 Add SSH Credential support to track where a credential is used Change By: D P Summary: Add SSH Credential support to track where a credential is used Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38826) Add support to track where a credential is used
Title: Message Title D P created an issue Jenkins / JENKINS-38826 Add support to track where a credential is used Issue Type: Improvement Assignee: stephenconnolly Components: ssh-credentials-plugin Created: 2016/Oct/07 7:52 PM Priority: Minor Reporter: D P credentials plug-in added support for tracking credentials usage, see JENKINS-20139. However the consumer plug-in needs an update to enable this. Please add support. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-24479) The vSphere cloud will not allow this slave to start at this time.
Title: Message Title D P edited a comment on JENKINS-24479 Re: The vSphere cloud will not allow this slave to start at this time. Since we started running into this we've been restarting Jenkins once or twice per week to clear this state . , but I haven't found an explicit trigger condition Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24479) The vSphere cloud will not allow this slave to start at this time.
Title: Message Title D P commented on JENKINS-24479 Re: The vSphere cloud will not allow this slave to start at this time. Since we started running into this we've been restarting Jenkins once or twice per week to clear this state. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24479) The vSphere cloud will not allow this slave to start at this time.
Title: Message Title D P commented on JENKINS-24479 Re: The vSphere cloud will not allow this slave to start at this time. Did this ever go anywhere? We may have just run into this issue, possibly triggered by a storage issue in vSphere. We got some failed startups due to the storage issue, but after clearing that out, slaves would still not start. The only thing in the slave log was "ERROR: The vSphere cloud will not allow this slave to start at this time.". As in this bug report, restarting Jenkins cleared it up Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
