[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Steve Todorov commented on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException Liam Newman Yes - we do have multibranch-defaults-plugin installed (as marked in the issue description) and we are specifically using the part of loading `Jenkinsfile`s using `Managed Files` on some of our jobs. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205962.1588001733000.23585.1588942560323%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Steve Todorov edited a comment on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException [~bitwiseman] Yes - we do have multibranch-defaults-plugin installed (as marked in the issue description) and we are specifically using the part of loading `Jenkinsfile`s using `Managed Files` on some of our jobs. I've actually tried removing the plugin just now and confirm it's part of the problem. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205962.1588001733000.23587.1588942560377%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Steve Todorov commented on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException Hi Liam Newman I've updated the environment info - we're using BlueOcean 1.23.0. I have tried downgrading Pipeline: Multibranch to 2.20 and Pipeline: Multibranch Defaults to 2.0, but it didn't fix it. I have a feeling it's another plugin is causing this issue but I can't seem to find which one. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205962.1588001733000.18695.1588035300139%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Steve Todorov updated an issue Jenkins / JENKINS-62063 BlueOcean UI is broken due to ClassCastException Change By: Steve Todorov Environment: Jenkins 2.233Pipeline: Multibranch with defaults: 2.1Pipeline: Multibranch: 2.21 Blue Ocean: 1.23.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205962.1588001733000.18688.1588034880209%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Steve Todorov updated an issue Jenkins / JENKINS-62063 BlueOcean UI is broken due to ClassCastException Change By: Steve Todorov Component/s: workflow-multibranch-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205962.1588001733000.18379.1588005720208%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BuileOcean UI is broken due to ClassCastException
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-62063 BuileOcean UI is broken due to ClassCastException Issue Type: Bug Assignee: Denis Saponenko Components: pipeline-multibranch-defaults-plugin Created: 2020-04-27 15:35 Environment: Jenkins 2.233 Pipeline: Multibranch with defaults: 2.1 Pipeline: Multibranch: 2.21 Priority: Blocker Reporter: Steve Todorov Most of our build jobs cannot be accessed through the Blue Ocean UI. For example accessing /blue/organizations/jenkins/pipelines triggers a request to /blue/rest/search/?q=type:pipeline;organization:jenkins;pipeline:;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject=no-folders=0=26 which then produces the following exception: Apr 27, 2020 3:23:45 PM WARNING hudson.init.impl.InstallUncaughtExceptionHandler handleException Caught unhandled exception with ID 3f5f1f8b-c409-4a3a-9ee8-9db8e549fd08 java.lang.ClassCastException:
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Steve Todorov updated an issue Jenkins / JENKINS-62063 BlueOcean UI is broken due to ClassCastException Change By: Steve Todorov Summary: BuileOcean BlueOcean UI is broken due to ClassCastException Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205962.1588001733000.18302.1588001760408%40Atlassian.JIRA.
[JIRA] (JENKINS-53032) Support dynamic definition of parallel running stages
Title: Message Title Steve Todorov edited a comment on JENKINS-53032 Re: Support dynamic definition of parallel running stages I've answered a similar question at [devops.stackexchange.com|https://devops.stackexchange.com/questions/9887/how-to-define-dynamic-parallel-stages-in-a-jenkinsfile]. I believe this is a bit overcomplicated and it should probably the Jenkins team should probably think of a way to simplify the way how dynamic stages (be they parallel or not) can be used in a declarative 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.193020.1534242389000.549.1577470142475%40Atlassian.JIRA.
[JIRA] (JENKINS-53032) Support dynamic definition of parallel running stages
Title: Message Title Steve Todorov commented on JENKINS-53032 Re: Support dynamic definition of parallel running stages I've answered a similar question at devops.stackexchange.com. I believe this is a bit overcomplicated and it should probably the Jenkins team should think of a way to simplify the way dynamic stages (be they parallel or not) can be used in a declarative 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.193020.1534242389000.545.1577469540170%40Atlassian.JIRA.
[JIRA] (JENKINS-59223) [Blue Ocean] Cannot write inside text parameters
Title: Message Title Steve Todorov updated an issue Jenkins / JENKINS-59223 [Blue Ocean] Cannot write inside text parameters Change By: Steve Todorov Component/s: pipeline 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.201680.1567600183000.6487.1567600860278%40Atlassian.JIRA.
[JIRA] (JENKINS-59223) [Blue Ocean] Cannot write inside text parameters
Title: Message Title Steve Todorov updated an issue Jenkins / JENKINS-59223 [Blue Ocean] Cannot write inside text parameters Change By: Steve Todorov We have been experiencing a very annoying issue with the new blue ocean UI. If you have a parameterized build and there is an `input type="text"` field anywhere in the parameters - it is impossible to enter anything inside that field. Once you click inside the text input the page redirects immediately to the latest build.I have attached a short video which demonstrates the issue. Workaround: If you right click inside the input field and then right click again - the cursor will appear and you should be able to write inside the input. P.S. I'm not very sure which is the "right" component, so apologize if it's the wrong one. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201680.1567600183000.6466.1567600320273%40Atlassian.JIRA.
[JIRA] (JENKINS-59223) [Blue Ocean] Cannot write inside text parameters
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-59223 [Blue Ocean] Cannot write inside text parameters Issue Type: Bug Assignee: Unassigned Attachments: cannot-write-in-inputs-2019-9-4-1567599555863.webm Components: blueocean-plugin Created: 2019-09-04 12:29 Environment: Jenkins ver. 2.192 Labels: user-experience Priority: Minor Reporter: Steve Todorov We have been experiencing a very annoying issue with the new blue ocean UI. If you have a parameterized build and there is an `input type="text"` field anywhere in the parameters - it is impossible to enter anything inside that field. Once you click inside the text input the page redirects immediately to the latest build. I have attached a short video which demonstrates the issue. P.S. I'm not very sure which is the "right" component, so apologize if it's the wrong one.
[JIRA] (JENKINS-58863) Builds cannot start after upgrading
Title: Message Title Steve Todorov updated JENKINS-58863 Jenkins / JENKINS-58863 Builds cannot start after upgrading Change By: Steve Todorov Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201178.1565282292000.2805.1567088100618%40Atlassian.JIRA.
[JIRA] (JENKINS-58863) Builds cannot start after upgrading
Title: Message Title Steve Todorov commented on JENKINS-58863 Re: Builds cannot start after upgrading Thanks for the reply Carlos Sanchez. It looks like JENKINS-58766 has resolved the issue indeed. Upgrading to 1.18.3 works fine for me so far. 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.201178.1565282292000.2798.1567087980967%40Atlassian.JIRA.
[JIRA] (JENKINS-58863) Builds cannot start after upgrading
Title: Message Title Steve Todorov commented on JENKINS-58863 Re: Builds cannot start after upgrading Carlos Sanchez ping - have you had any time to check this out 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201178.1565282292000.920.1566926880590%40Atlassian.JIRA.
[JIRA] (JENKINS-58886) Project base security matrix allows wrong group of users access
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-58886 Project base security matrix allows wrong group of users access Issue Type: Bug Assignee: Unassigned Attachments: image-2019-08-11-12-36-30-465.png Components: core, ldap-plugin Created: 2019-08-11 09:52 Environment: Jenkins 2.189 LDAP Priority: Blocker Reporter: Steve Todorov We have a folder with projects inside which have `project-based security` enabled and the Inheritance Strategy is set to `Inherit from parent`. The folder's permissions are: In the screenshot above I've added `myname-noaccess` just to illustrate the group permissions - in reality it is missing in the configuration. The problem is that the users from the `myname-noaccess` group, although not configured anywhere, are able to see the all of projects within the folder. While trying to figure out the issue, I noticed that `myname-noaccess` users actually have the same permissions as the `myname` group and once I removed it the folder and projects inside stopped appearing for `myname-noaccess`. I believe there might be an issue with how the permissions are being detected - most likely there is a wildcard somewhere. The temporary fix is to rename `myname` group to something like `myname-core`.
[JIRA] (JENKINS-58863) Builds cannot start after upgrading
Title: Message Title Steve Todorov updated an issue Jenkins / JENKINS-58863 Builds cannot start after upgrading Change By: Steve Todorov Attachment: jenkins.log 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.201178.1565282292000.16.1565372040365%40Atlassian.JIRA.
[JIRA] (JENKINS-58863) Builds cannot start after upgrading
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-58863 Builds cannot start after upgrading Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-08-08 16:38 Environment: Jenkins: 2.189 Kubernetes Plugin: 1.18.1 Priority: Critical Reporter: Steve Todorov After upgrading to the latest Kubernetes plugin we have started receiving this exception and no jobs can be built: sh: cd: line 1: can't cd to /home/jenkins/workspace/abcd_master: No such file or directory sh: can't create /home/jenkins/workspace/abcd_master@tmp/durable-9ae82b18/jenkins-log.txt: nonexistent directory sh: can't create /home/jenkins/workspace/abcd_master@tmp/durable-9ae82b18/jenkins-result.txt.tmp: nonexistent directory mv: cannot stat '/home/jenkins/workspace/abcd_master@tmp/durable-9ae82b18/jenkins-result.txt.tmp': No such file or directory process apparently never started in /home/jenkins/workspace/abcd_master@tmp/durable-9ae82b18 script returned exit code -2 An agent is being allocated, the job is running on it, but for some unknown reason it can't execute anything. Nothing has changed in our docker images so this is not a permission issue (and we have enough space on the nodes so it's not that as well) Downgrading back to 1.17.3 fixes the issue and everything works just fine.
[JIRA] (JENKINS-57569) Can't boot Jenkins since upgrade to 2.178
Title: Message Title Steve Todorov commented on JENKINS-57569 Re: Can't boot Jenkins since upgrade to 2.178 We are using Jenkins with LDAP as well and upgrading from 2.174 to 2.178 was successful. LDAP Authentication is working just fine for us. We are also using the latest versions of all plugins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199483.1558376853000.8536.1558519800822%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57200) Can't access builds in BlueOcean after updating to 1.15.0
Title: Message Title Steve Todorov commented on JENKINS-57200 Re: Can't access builds in BlueOcean after updating to 1.15.0 Many thanks for fixing this Gavin Mogan! Works as expected! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57200) Can't access builds in BlueOcean after updating to 1.15.0
Title: Message Title Steve Todorov edited a comment on JENKINS-57200 Re: Can't access builds in BlueOcean after updating to 1.15.0 Hi [~halkeye], thanks for your reply! It looks like you might be on the right track - I have replayed a few builds in the job. It looks like BlueOcean is working fine for new `PR`s and `Branches`. Would you be able to make a patch for this? I can test it once it's available. 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-57200) Can't access builds in BlueOcean after updating to 1.15.0
Title: Message Title Steve Todorov commented on JENKINS-57200 Re: Can't access builds in BlueOcean after updating to 1.15.0 Hi Gavin Mogan, thanks for your reply! It looks like you might be on the right track - I have replayed a few builds in the job. It looks like BlueOcean is working fine for new `PR`s and `Branches`. Would be able to make a patch for this? I can test it once it's available. 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-57200) Can't access builds in BlueOcean after updating to 1.15.0
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-57200 Can't access builds in BlueOcean after updating to 1.15.0 Issue Type: Bug Assignee: Unassigned Attachments: jenkins-thread-dump.log Components: core Created: 2019-04-26 20:44 Environment: Jenkins 2.174 (running in docker container) All BlueOcean plugins at 1.15.0 Labels: jenkins blueocean blueocean-ui Priority: Critical Reporter: Steve Todorov We've upgraded our BlueOcean plugins to the latest 1.15.0 and restarted Jenkins. Afterward, we were unable to access the `activity` tab and some of the builds. Initially we thought it was a browser issue, but after doing a curl request we noticed it's not working as well: $ time curl -I https://domain.com/blue/organizations/jenkins/project%2FjobName/detail/master/2217/pipeline/ ^C real 3m53,812s user 0m0,010s sys 0m0,008s There are no exception logs in Jenkins which can point to what's causing this. However I did make a thread dump which I've attached. I wasn't sure which component this relates to exactly so I've marked `core`.
[JIRA] (JENKINS-56259) Allow input timeout parameter
Title: Message Title Steve Todorov commented on JENKINS-56259 Re: Allow input timeout parameter Mark Vinkx Yes, you could wrap the input like that, but unfortunately this means that you will allocate an agent and have it do nothing for 5 minutes. Also the Blue Ocean UI would display this stage as "passed" (green) which will be (and is) confusing, because you never know if the stage has actually passed or it has been skipped/not approved - you will need to specifically go into the stage to check the steps, whereas if you have it as a stage input it would show in the UI as skipped. Jesse Glick yes, you've understood me correctly 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-40703) Support injection of maven-gpg-plugin:sign config params in Maven Settings files
Title: Message Title Steve Todorov edited a comment on JENKINS-40703 Re: Support injection of maven-gpg-plugin:sign config params in Maven Settings files [~cleclerc] do you know what is the state of this issue? We are currently preparing some jobs which will be using the `maven-gpg-plugin` to sign maven artifacts. However the only way this would ever work is by doing `mvn release:perform -Darguments=-Dgpg.passphrase=thephrase` and passing the password via the CLI is something we would like to avoid.Can't there just be a `Maven passphrase` credential type for this case kind which results you can add in adding a server Id with a the credentials section and then from the ` Config File Management ` ? (like in you can add the [examples|http://maven.apache.org/plugins/maven-gpg-plugin/usage.html] of maven's gpg plugin) `serverid` to use the defined credentials? 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-40703) Support injection of maven-gpg-plugin:sign config params in Maven Settings files
Title: Message Title Steve Todorov commented on JENKINS-40703 Re: Support injection of maven-gpg-plugin:sign config params in Maven Settings files Cyrille Le Clerc do you know what is the state of this issue? We are currently preparing some jobs which will be using the `maven-gpg-plugin` to sign maven artifacts. However the only way this would ever work is by doing `mvn release:perform -Darguments=-Dgpg.passphrase=thephrase` and passing the password via the CLI is something we would like to avoid. Can't there just be a `Maven passphrase` credential type for this case which results in adding a server Id with a `` ? (like in the examples of maven's gpg plugin) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56259) Allow input timeout parameter
Title: Message Title Steve Todorov commented on JENKINS-56259 Re: Allow input timeout parameter Jesse Glick thanks for fixing that! Apologize for the wrong component 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-36235) Add optional 'timeout' parameter to 'input' step
Title: Message Title
Steve Todorov commented on JENKINS-36235
Re: Add optional 'timeout' parameter to 'input' step
I really don't know why is this marked as "fixed". I've opened another ticket about the same issue - https://issues.jenkins-ci.org/browse/JENKINS-56259 It would be really great if there was a parameter for the `input` step. You cannot wrap this in a `timeout` when you are using it at a `stage(){ input {} }` level in a declarative pipeline.
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-36235) Add optional 'timeout' parameter to 'input' step
Title: Message Title
Steve Todorov edited a comment on JENKINS-36235
Re: Add optional 'timeout' parameter to 'input' step
I really don't know why is this marked as "fixed /won't fix ". I've opened another ticket about the same issue - https://issues.jenkins-ci.org/browse/JENKINS-56259 It would be really great if there was a parameter for the `input` step. You cannot wrap this in a `timeout` when you are using it at a `stage()\{ input {} }` level in a declarative pipeline.
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-56259) Allow input timeout parameter
Title: Message Title
Steve Todorov created an issue
Jenkins / JENKINS-56259
Allow input timeout parameter
Issue Type:
Improvement
Assignee:
Unassigned
Components:
pipeline, pipeline-input-step-plugin
Created:
2019-02-24 22:06
Priority:
Minor
Reporter:
Steve Todorov
I have been wondering for ages why is there no `timeout` option in the `input` step? I am aware you can wrap your input in a `timeout() {}`, but that is just impossible when you are using the `input` as part of the stage like so:
pipeline {
agent any
stages {
stage('Example') {
input {
message "Should we continue?"
ok "Yes, we should."
submitter "alice,bob"
parameters {
string(name: 'PERSON', defaultValue: 'Mr Jenkins', description: 'Who should I say hello to?')
}
}
steps {
echo "Hello, ${PERSON}, nice to meet you."
}
}
}
}
(Taken from https://jenkins.io/blog/2018/04/09/whats-in-declarative/#input) The possible "workaround" to this would be to create an `input` step in a previous stage which is wrapped in a `timeout` step, but in our case this makes things even more complicated and hard to read. Are there any plans to include an `timeout` parameter for the `input` step? Maybe something like this (or better?):
input {
message "Should we continue?"
ok "Yes, we should."
submitter "alice,bob"
timeout: [time: 1234, unit:
[JIRA] (JENKINS-54197) Allow combining site and room fields
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-54197 Allow combining site and room fields Issue Type: Improvement Assignee: Naresh Rayapati Components: hubot-steps-plugin Created: 2018-10-23 01:57 Priority: Minor Reporter: Steve Todorov Currently you are limited to using either `site` or the `room` fields. You cannot combine them. This is not very convenient, because you might want to configure multiple `sites` globally and then just fine-tune the `room` in the specific job's pipeline. Consider the following example: hubotSend message: 'Releasing Test project.', site: 'devops-report-site', status: 'FAILURE', room: 'devops' Add Comment
[JIRA] (JENKINS-40484) Unable to use withMaven() step inside docker container for old versions of Docker
Title: Message Title Steve Todorov edited a comment on JENKINS-40484 Re: Unable to use withMaven() step inside docker container for old versions of Docker ++[~acejam] try reverting to an older version of Docker Pipeline. I have been using the older version since this issue hit me in [ JENKINS-47805 |https://issues . jenkins-ci.org/browse/JENKINS-47805]. It seems that you can fix this either by using a mvnw, downgrade to an older version of Docker Pipeline or wait for [ JENKINS-48050 |https://issues which looks like it will fix it for good . jenkins-ci.org/browse/JENKINS-48050]. 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-40484) Unable to use withMaven() step inside docker container for old versions of Docker
Title: Message Title Steve Todorov commented on JENKINS-40484 Re: Unable to use withMaven() step inside docker container for old versions of Docker ++Joshua Noble try reverting to an older version of Docker Pipeline. I have been using the older version since this issue hit me in JENKINS-47805. It seems that you can fix this either by using a mvnw, downgrade to an older version of Docker Pipeline or wait for JENKINS-48050. 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-50652) Aborting a sh or bat step fires both aborted and failure post conditions
Title: Message Title Steve Todorov commented on JENKINS-50652 Re: Aborting a sh or bat step fires both aborted and failure post conditions Thanks for your quick fix! Let me know if there is going to be a snapshot release which I could test. 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-50652) Post stages are incorrectly handled
Title: Message Title
Steve Todorov updated an issue
Jenkins / JENKINS-50652
Post stages are incorrectly handled
Change By:
Steve Todorov
Consider the following example:{code:java}pipeline { agent { label 'linux' } stages {stage('Successful stage') { steps {script { sh "sleep 15" // intentionally not using sleep 15 step!} }} } post {success { echo "Triggered post-success"}failure { echo "Triggered post-failure"}unstable { echo "Triggered post-unstable"}aborted { echo "Triggered post-aborted"} }}{code}Start the build, let it go into "sleep" and abort the build. The result will be:{code:java}[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] echoTriggered post-aborted[Pipeline] echoTriggered post-failure[Pipeline] }{code} The result is having both `post-aborted` and `post-failure` executed. What should have happened was to receive only `post-aborted` step. I've also seen in the logs `post-unstable` and `post-failure`, but I am not sure how to provide a way to reproduce this. I'm not sure how that happened but I have seen it a few times on some of our builds.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50652) Post stages are incorrectly handled
Title: Message Title Steve Todorov commented on JENKINS-50652 Re: Post stages are incorrectly handled Sorry for the delayed reply. The issue is that both the post-abort and post-failure steps are triggered when you abort a build. What should have happened was to receive only post-abort when you hit the Abort button. In our case we are trying to execute specific steps only for post-abort and other specific steps only for post-failure, however we end up having both steps for post-abort and post-failure executed which is messing things up. 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-50652) Post stages are incorrectly handled
Title: Message Title
Steve Todorov created an issue
Jenkins / JENKINS-50652
Post stages are incorrectly handled
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-04-08 18:06
Priority:
Major
Reporter:
Steve Todorov
Consider the following example:
pipeline {
agent {
label 'linux'
}
stages {
stage('Successful stage') {
steps {
script {
sh "sleep 15" // intentionally not using sleep 15 step!
}
}
}
}
post {
success {
echo "Triggered post-success"
}
failure {
echo "Triggered post-failure"
}
unstable {
echo "Triggered post-unstable"
}
aborted {
echo "Triggered post-aborted"
}
}
}
Start the build, let it go into "sleep" and abort the build. The result will be:
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] echo
Triggered post-aborted
[Pipeline] echo
Triggered post-failure
[Pipeline] }
I've also seen in the logs `post-unstable` and `post-failure`, but I am not sure how to provide a way to reproduce this. I'm not sure how that happened but I have seen it a few times on some of our builds.
[JIRA] (JENKINS-50432) Global limit of maximum agents that can be dynamically allocated in a docker swarm
Title: Message Title Steve Todorov commented on JENKINS-50432 Re: Global limit of maximum agents that can be dynamically allocated in a docker swarm surya gaddipati thank you very much for your reply. This seems to be solving the issue so far. We were using the `limit` without `reserve` which was causing the issue. I think we can close this now. 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-50432) Global limit of maximum agents that can be dynamically allocated in a docker swarm
Title: Message Title Steve Todorov updated an issue Jenkins / JENKINS-50432 Global limit of maximum agents that can be dynamically allocated in a docker swarm Change By: Steve Todorov Issue Type: Bug Improvement 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-50432) Global limit of maximum agents that can be dynamically allocated in a docker swarm
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-50432 Global limit of maximum agents that can be dynamically allocated in a docker swarm Issue Type: Bug Assignee: surya gaddipati Components: docker-swarm-plugin Created: 2018-03-27 13:08 Environment: Docker: 17.04-ce Linux: OpenSUSE Jenkins: 2.111 Docker Swarm Plugin: 1.5 Labels: docker swarm Priority: Major Reporter: Steve Todorov We have been using this plugin to dynamically provision our agents in a docker container for our builds. Everything has been working quite well so far! However, the is one small issue we're hitting - you can have unlimited jobs which request agents. This is an awesome feature, but our bare-metal cloud is definitely not unlimited so we eventually hit the limit to the machines every now and then. Would it be possible to have a field in which you can set a global limit for the maximum amount of containers the swarm can handle? And when you get over the limit the plugin would wait until the running containers are below that number.
[JIRA] (JENKINS-45385) currentBuild.result is not properly set to ABORTED when a build is aborted (withMaven)
Title: Message Title Steve Todorov assigned an issue to Alvaro Lobato Jenkins / JENKINS-45385 currentBuild.result is not properly set to ABORTED when a build is aborted (withMaven) Change By: Steve Todorov Assignee: Alvaro Lobato 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-50157) Zip step fails to execute and dies with syntax error in a parallel stage with post step
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-50157 Zip step fails to execute and dies with syntax error in a parallel stage with post step Issue Type: Bug Assignee: rsandell Attachments: error.log, Jenkinsfile Components: pipeline-utility-steps-plugin Created: 2018-03-14 00:04 Environment: Docker Container Alpine 3.7 Jenkins 2.101 pipeline-utility-steps-2.0.1 Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00) Maven home: /java/mvn-3.3.9 Java version: 1.8.0_161, vendor: Oracle Corporation Java home: /java/jdk-1.8u161-b12/jre Default locale: en, platform encoding: UTF-8 OS name: "linux", version: "4.15.7-2.g353046a-default", arch: "amd64", family: "unix" Priority: Minor Reporter: Steve Todorov We have a Jenkins job which tests out product using different tools such as sbt, maven, gradle and so on. Our build runs in parallel on multiple nodes and we wanted to "zip" some artifacts from the target directories for easier debugging. According to the documentation (as well as the generated Pipeline snippet from the Pipeline Syntax page) the following line should be working just fine: zip archive: true, dir: './maven/target', glob: '', zipFile: 'maven-target.zip' Unfortunately this is not the case
[JIRA] (JENKINS-48050) Replace Declarative Docker agent directive with new implementation
Title: Message Title Steve Todorov commented on JENKINS-48050 Re: Replace Declarative Docker agent directive with new implementation Thanks for your reply. Please keep us in the loop in that case. 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-48050) Replace Declarative Docker agent directive with new implementation
Title: Message Title Steve Todorov commented on JENKINS-48050 Re: Replace Declarative Docker agent directive with new implementation This seems like it will fix a lot of the issues we're having with running maven builds in docker containers. What is the approximate timeline for having this feature released - I'm guessing a few months? 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-40092) slave.jar copy via SCP fails in 2.33+
Title: Message Title Steve Todorov commented on JENKINS-40092 Re: slave.jar copy via SCP fails in 2.33+ Jesse Glick this release seems to have fixed the issue. I've upgraded to jenkins 2.34 and the latest SSH slaves plugin and everything works fine. Thanks for your fast fix! 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-40092) can not copy slave.jar after upgrade from 2.31 to 2.34
Title: Message Title Steve Todorov commented on JENKINS-40092 Re: can not copy slave.jar after upgrade from 2.31 to 2.34 Jesse Glick I managed to get our slaves to work by downgrading Jenkins from 2.34 to 2.31 and Yet Another Docker Plugin from 0.1.0-rc30 to 0.1.0-rc29. Now everything seems to be working as usual. I haven't made any changes to our docker slaves. The interesting thing is that our opensuse docker slave was working fine, but ubuntu/debian/centos were getting the exception above. If you like, I can give you a slightly modified version of our Dockerfile for centos/ubuntu/debian so you can use it to test sometime tomorrow? 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-40092) can not copy slave.jar after upgrade from 2.31 to 2.34
Title: Message Title Steve Todorov edited a comment on JENKINS-40092 Re: can not copy slave.jar after upgrade from 2.31 to 2.34 I confirm having the exact same issue as well. We're running Jenkins 2.34 on OpenSUSE 42.1, Java version: 1.8.0_92, vendor: Oracle Corporation. Our nodes are being delivered via docker and are running CentOS, Ubuntu and Debian. The SSH it working fine on all of the nodes - I can login using the jenkins user, I can use SCP / SFTP to transfer files without any problems. There is also enough space on all of the nodes (including the master).P.S. Downgrading to 2.31 did not help. 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-40092) can not copy slave.jar after upgrade from 2.31 to 2.34
Title: Message Title Steve Todorov commented on JENKINS-40092 Re: can not copy slave.jar after upgrade from 2.31 to 2.34 I confirm having the exact same issue as well. We're running Jenkins 2.34 on OpenSUSE 42.1, Java version: 1.8.0_92, vendor: Oracle Corporation. Our nodes are being delivered via docker and are running CentOS, Ubuntu and Debian. The SSH it working fine on all of the nodes - I can login using the jenkins user, I can use SCP / SFTP to transfer files without any problems. There is also enough space on all of the nodes (including the master). 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-39437) Configure page broken after update to 2.28 version
Title: Message Title Steve Todorov commented on JENKINS-39437 Re: Configure page broken after update to 2.28 version We're also experiencing this problem. We can't open the configuration page - the same exception is shown. If you scroll to the end you can see the form fields, but it looks like you can't save anything. 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.
