[JIRA] (JENKINS-52280) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Oleg Nenashev commented on JENKINS-52280 Re: Create official Java 11 Docker Packaging for BlueOcean Adrien Lecharpentier: Having separate repo may be a problem Oleg: We could replace https://github.com/jenkinsci/blueocean-plugin/blob/master/Dockerfile.jdk10 by the new file and make it a part of the Default build by the Docker team 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-52280) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52280 Create official Java 11 Docker Packaging for BlueOcean Change By: Oleg Nenashev During the hackathon we have created [ https://github.com/jenkinsci/blueocean-plugin/blob/master/Dockerfile.jdk10 ] . Now it needs to be expanded to Java 11 and added to the common release flows Acceptance: * Promote [https://github.com/oleg-nenashev/jenkins-blueocean-experimental] to jenkinsci * Setup new DockerHub repo with Automatic build, e.g. jenkins/blueocean which is unused * Define naming strategy * Create Java 8 and Java 11 branches there, similar to the source repo * Update jenkins.io documentation to reflect the new repo: [https://jenkins.io/doc/book/installing/#downloading-and-running-jenkins-in-docker] It needs agreement with the BlueOcean team. 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-54451) Jenkins Set a banner message
Title: Message Title Daniel Beck closed an issue as Not A Defect The feature exists. It's called "System Message" in the global configuration. Hence this is a request for help, and not a bug or feature request. Please read https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue – you're on the wrong site. Jenkins / JENKINS-54451 Jenkins Set a banner message Change By: Daniel Beck Status: Reopened Closed Resolution: Not A Defect 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-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E edited a comment on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down I got this too.Short-term workaround, either of the following under "Orphaned Item Strategy": * Switch off "Discard old items" entirely, and take care of that by hand * Set positive number in "Max # of old items to keep"/"Days to keep old items".Your mileage may vary depending on how often your Mercurial server goes down.Having dug into this a bit, I believe the orphaned item stuff is behaving as expected.The curious bit is the "Could not use caches, not fetching branch heads" error. Looking in [MercurialSCMSource.java|https://github.com/jenkinsci/mercurial-plugin/blob/65ba1fe95fc95670a153a551b434d26365a0130c/src/main/java/hudson/plugins/mercurial/MercurialSCMSource.java#L211], it the retrieve methods simply returns if the cache is null. Should this not be throwing an exception instead? The knock-on effect seems to be that the orphaned item strategy kicks in and all the branches are marked as closed. I would expect the polling/indexing to abort entirely if the cache is not available/working. 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-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E edited a comment on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down I got this too.Short-term workaround, either of the following under "Orphaned Item Strategy": * Switch off "Discard old items" entirely, and take care of that by hand * Set positive number in "Max # of old items to keep"/"Days to keep old items".Your mileage may vary depending on how often your Mercurial server goes down.Having dug into this a bit, I believe the orphaned item stuff is behaving as expected.The curious bit is the "Could not use caches, not fetching branch heads" error. Looking in [MercurialSCMSource.java| https://github.com/jenkinsci/mercurial-plugin/blob/65ba1fe95fc95670a153a551b434d26365a0130c/src/main/java/hudson/plugins/mercurial/MercurialSCMSource.java #L211], ] it simply returns if the cache is null. Should this not be throwing an exception instead? The knock-on effect seems to be that the orphaned item strategy kicks in and all the branches are marked as closed. I would expect the polling/indexing to abort entirely if the cache is not available/working. 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-51985) Create official jenkins/jenkins Docker images for Java 10 and 11 versions
Title: Message Title Oleg Nenashev commented on JENKINS-51985 Re: Create official jenkins/jenkins Docker images for Java 10 and 11 versions The proposal is to go with the option 1 right now, because it saves a lot of time 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-51985) Create official jenkins/jenkins Docker images for Java 10 and 11 versions
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51985 Create official jenkins/jenkins Docker images for Java 10 and 11 versions Change By: Oleg Nenashev In [https://github.com/jenkinsci/docker/pull/690/commits/ffe36e0f9d6d94b1c10e2fc71751e5fbba0a26f4] and [https://github.com/jenkinsci/docker/pull/690] only base images have been adjusted to Java 10 and 11 (in java10 and java11 branches). We need to upstream these changes and integrate into the common weekly release flow.It would be also great to update Alpine and Slim images as well so that they can be shipped within the common release flow (if possible & feasible).Attack plan 1: additional Dockerfile in the repo * Take [https://github.com/jenkinsci/docker/blob/java11/Dockerfile] and put it to master (Dockerfile-jdk11) * Update scripts to also build and publish Java 11 * Risk: The build runs on Trusted CI, may need help from [~olblak] . May have issues with debugging * Possible resolution: parameterize scripts and deploy to jenkins4eval (for local debugging). [~oleg_nenashev] can help with permissionsAttack plan 2: via multi-platform * Get [https://github.com/jenkinsci/docker/pull/719] integrated * Upstream Java 11 support patches from [https://github.com/jenkinsci/remoting/pull/292] to the master scripts * Enable the new build mode on trusted-ci which can deploy images Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-51985) Create official jenkins/jenkins Docker images for Java 10 and 11 versions
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51985 Create official jenkins/jenkins Docker images for Java 10 and 11 versions Change By: Oleg Nenashev In [https://github.com/jenkinsci/docker/pull/690/commits/ffe36e0f9d6d94b1c10e2fc71751e5fbba0a26f4] and [https://github.com/jenkinsci/docker/pull/690] only base images have been adjusted to Java 10 and 11 (in java10 and java11 branches). We need to upstream these changes and integrate into the common weekly release flow.It would be also great to update Alpine and Slim images as well so that they can be shipped within the common release flow (if possible & feasible). Attack plan 1: * Take [https://github.com/jenkinsci/docker/blob/java11/Dockerfile] and put it to master * Update scripts to also build and publish Java 11 * Risk: The build runs on Trusted CI, may need help from [~olblak] . May have issues with debugging * Possible resolution: parameterize scripts and deploy to jenkins4eval (for local debugging). [~oleg_nenashev] can help with permissions Attack plan 2 : * Get [https://github.com/jenkinsci/docker/pull/719] integrated * Upstream Java 11 support patches from [https://github.com/jenkinsci/remoting/pull/292] to the master scripts * Enable the new build mode on trusted-ci which can deploy images Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You recei
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Joerg Schwaerzler commented on JENKINS-51143 Re: List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Timothy Bingaman, Sven Schoenung: We're still preparing the PR which initially was created by Moritz Knolle - we're almost done. Wonder whether so else is working on that topic as well. Please let us know. 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-54451) Jenkins Set a banner message
Title: Message Title Rakesh Nagarajan updated an issue Jenkins / JENKINS-54451 Jenkins Set a banner message Change By: Rakesh Nagarajan Attachment: image-2018-11-09-15-28-20-204.png 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-54451) Jenkins Set a banner message
Title: Message Title Rakesh Nagarajan commented on JENKINS-54451 Re: Jenkins Set a banner message Something just like 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-54553) Jenkins to disable editing security from UI (even for admins)
Title: Message Title Rakesh Nagarajan started work on JENKINS-54553 Change By: Rakesh Nagarajan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54554) Jenkins CLI is not working in reverse proxy (traefik)
Title: Message Title Rakesh Nagarajan started work on JENKINS-54554 Change By: Rakesh Nagarajan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54554) Jenkins CLI is not working in reverse proxy (traefik)
Title: Message Title Rakesh Nagarajan commented on JENKINS-54554 Re: Jenkins CLI is not working in reverse proxy (traefik) CLI is working fine in SSH. But unfortunately it is not working through http. -auth command is not recognizing in this case. Do we need to use crumb ? 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-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E commented on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down It doesn't help that the next consequence of this is a build storm when the mercurial server comes back up. All branches are marked as reopened and everything rebuilds. We currently have some issues with our hg server, and it reboots several times a week, so the build storms are proving to be the most frustrating consequence. 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-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E edited a comment on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down I got this too.Short-term workaround, either of the following under "Orphaned Item Strategy": * Switch off "Discard old items" entirely, and take care of that by hand * Set positive number in "Max # of old items to keep"/"Days to keep old items".Your mileage may vary depending on how often your Mercurial server goes down.Having dug into this a bit, I believe the orphaned item stuff is behaving as expected.The curious bit is the "Could not use caches, not fetching branch heads" error. Looking in [MercurialSCMSource.java| [https://github.com/jenkinsci/mercurial-plugin/blob/65ba1fe95fc95670a153a551b434d26365a0130c/src/main/java/hudson/plugins/mercurial/MercurialSCMSource.java #L211],] it simply returns if the cache is null. Should this not be throwing an exception instead? The knock-on effect seems to be that the orphaned item strategy kicks in and all the branches are marked as closed. I would expect the polling /indexing to abort entirely if the cache is not available/working. 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-54554) Jenkins CLI is not working in reverse proxy (traefik)
Title: Message Title Rakesh Nagarajan created an issue Jenkins / JENKINS-54554 Jenkins CLI is not working in reverse proxy (traefik) Issue Type: Task Assignee: Unassigned Components: core Created: 2018-11-09 09:47 Priority: Minor Reporter: Rakesh Nagarajan Hi Team, We have a docker swarm cluster setup, all the jenkins containers created in the docker is managed by traefik. Problem is "Jenkins CLI is not working in this". But without traefik, its working fine. Is this related to fullduplex ? is there any alternative way ? even if we enabled "enable remote CLI" it is not helping us. Add Comment
[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E commented on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down I got this too. Short-term workaround, either of the following under "Orphaned Item Strategy": Switch off "Discard old items" entirely, and take care of that by hand Set positive number in "Max # of old items to keep"/"Days to keep old items". Your mileage may vary depending on how often your Mercurial server goes down. Having dug into this a bit, I believe the orphaned item stuff is behaving as expected. The curious bit is the "Could not use caches, not fetching branch heads" error. Looking in MercurialSCMSource.java it simply returns if the cache is null. Should this not be throwing an exception instead? The knock-on effect seems to be that the orphaned item strategy kicks in and all the branches are marked as closed. I would expect the polling to abort entirely if the cache is not available/working. 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-54451) Jenkins Set a banner message
Title: Message Title Rakesh Nagarajan assigned an issue to Rakesh Nagarajan Jenkins / JENKINS-54451 Jenkins Set a banner message Change By: Rakesh Nagarajan Assignee: Rakesh Nagarajan 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-54451) Jenkins Set a banner message
Title: Message Title Rakesh Nagarajan commented on JENKINS-54451 Re: Jenkins Set a banner message I found an alternative way for doing this. jenkins --> manage jenkins --> prepare for shut down a new pop-up will come up "JENKINS IS GOING TO SHUTDOWN" (But if we do so, then no other jobs will run) Which java function is doing this job? if we can find the function alone, we can modify the wordings and analyze the script. 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-54553) Jenkins to disable editing security from UI (even for admins)
Title: Message Title Rakesh Nagarajan created an issue Jenkins / JENKINS-54553 Jenkins to disable editing security from UI (even for admins) Issue Type: Task Assignee: Unassigned Attachments: image-2018-11-09-15-07-03-793.png Components: core Created: 2018-11-09 09:37 Priority: Minor Reporter: Rakesh Nagarajan Hi Team, I am facing an issue, we have given admin rights to several users in jenkins. But due to some reasons, some one is removing our user id from accessing the jenkins (even i am also an admin in jenkins) Is there any option for resolving this issue. Add Comment
[JIRA] (JENKINS-54451) Jenkins Set a banner message
Title: Message Title Rakesh Nagarajan reopened an issue This is also an issue. I am working on this Jenkins / JENKINS-54451 Jenkins Set a banner message Change By: Rakesh Nagarajan Resolution: Not A Defect Status: Closed Reopened 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-54552) code analyzer tool exe to analyze the code and generate the excel file
Title: Message Title praveen kumar created an issue Jenkins / JENKINS-54552 code analyzer tool exe to analyze the code and generate the excel file Issue Type: Task Assignee: Michael Fowler Attachments: Jenkins.png Components: windows-exe-runner-plugin Created: 2018-11-09 09:20 Environment: DEv Labels: jenkins windows Priority: Critical Reporter: praveen kumar Hi team, We are working on COde analyzer tool to run the exe and analyze the openspan(RPA) code and get the results in excel file. We are running batch file and running using commands and we are getting success and not generating the excel file in specified folder. Please help us on with solution. Thanks Praveen K.
[JIRA] (JENKINS-54551) Revert JENKINS-53462 if necessary
Title: Message Title Daniel Beck resolved as Fixed Resolving to make this show up in the LTS filter. Jenkins / JENKINS-54551 Revert JENKINS-53462 if necessary Change By: Daniel Beck Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54551) Revert JENKINS-53462 if necessary
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-54551 Revert JENKINS-53462 if necessary Issue Type: Bug Assignee: Oliver Gondža Components: core Created: 2018-11-09 09:15 Labels: lts-candidate Priority: Minor Reporter: Daniel Beck Tracking the potential need to revert the fix for JENKINS-53462 towards 2.150.1 because of the regressions it caused (linked there). Add Comment
[JIRA] (JENKINS-48694) Notifies successful build when still in progress
Title: Message Title Søren Friis commented on JENKINS-48694 Re: Notifies successful build when still in progress **2.2.14 seems to fix the problem we were facing. 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-53644) Is it possible to configure the color of the job (success or not) depending on the error number of one parser
Title: Message Title iostrym commented on JENKINS-53644 Re: Is it possible to configure the color of the job (success or not) depending on the error number of one parser done, thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54550) Add usage of new Error severity in Quality Gate Thresholds
Title: Message Title iostrym created an issue Jenkins / JENKINS-54550 Add usage of new Error severity in Quality Gate Thresholds Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-11-09 09:03 Environment: Jenkins 2.121.2 + warning plug-in version 5.X (beta) Priority: Critical Reporter: iostrym I have a problem because I can only set threshold for : Severity High / normal / low And it seems that it correspond only to WARNING_HIGH, WARNING_NORMAL, WARNING_LOW severity. And I don't succeed to make my job failing when I have at least one ERROR. Is it normal ? My parser only generates warning with severity : "Low" or "Error". Is it possible to use Quality Gate Thresholds on "Error" severity ? Because if I'm correct, Severity High is WARNING_HIGH and not Error. Am I correct ? Add Comment
[JIRA] (JENKINS-53405) Support of "customWorkspace" is missing for kubernets-plugin
Title: Message Title Bahram Parsapour commented on JENKINS-53405 Re: Support of "customWorkspace" is missing for kubernets-plugin Winfried Wasser did you had a chance to test the latest version of the plugin? If so, does it solve your problems described 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-14463) email ext plugin : full console log mail
Title: Message Title Vijayakumar Shanmugam commented on JENKINS-14463 Re: email ext plugin : full console log mail santhosh s Thanks a lot. That worked. I was struggling to get the correct syntax to use in my DSL 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-48694) Notifies successful build when still in progress
Title: Message Title Rasmus Pedersen commented on JENKINS-48694 Re: Notifies successful build when still in progress I tried version 2.2.14 and it doesn't cover all cases, but probably most. If there's no checkout scm step, like in stage 1 above, it is still reporting a successful build after completing stage 1 and then failing the build after stage 2. If checkout scm is added as the first step in stage 1 the status is now reported 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-52032) Replace slave occurrence by agent in the Amazon ECS plugin
Title: Message Title Philipp Garbe updated JENKINS-52032 Jenkins / JENKINS-52032 Replace slave occurrence by agent in the Amazon ECS plugin Change By: Philipp Garbe 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54428) ECS plugin fails if task definition ARN is used
Title: Message Title Philipp Garbe updated JENKINS-54428 Jenkins / JENKINS-54428 ECS plugin fails if task definition ARN is used Change By: Philipp Garbe Status: Open Fixed but Unreleased Resolution: Fixed Released As: v1.18 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-51775) New ECS task definition created for each instance of an Agent requested
Title: Message Title Philipp Garbe closed an issue as Fixed Jenkins / JENKINS-51775 New ECS task definition created for each instance of an Agent requested Change By: Philipp Garbe Status: Resolved Closed 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-52032) Replace slave occurrence by agent in the Amazon ECS plugin
Title: Message Title Philipp Garbe assigned an issue to Philipp Garbe Jenkins / JENKINS-52032 Replace slave occurrence by agent in the Amazon ECS plugin Change By: Philipp Garbe Assignee: Jan Roehrich Philipp Garbe 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-51775) New ECS task definition created for each instance of an Agent requested
Title: Message Title Philipp Garbe updated JENKINS-51775 Jenkins / JENKINS-51775 New ECS task definition created for each instance of an Agent requested Change By: Philipp Garbe Status: Fixed but Unreleased Resolved 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-51775) New ECS task definition created for each instance of an Agent requested
Title: Message Title Philipp Garbe updated JENKINS-51775 Jenkins / JENKINS-51775 New ECS task definition created for each instance of an Agent requested Change By: Philipp Garbe Status: Open Fixed but Unreleased Resolution: Fixed Released As: v1.17 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-45833) Can not spin up JNLP agent on Amazon ECS
Title: Message Title Philipp Garbe assigned an issue to Philipp Garbe Jenkins / JENKINS-45833 Can not spin up JNLP agent on Amazon ECS Change By: Philipp Garbe Assignee: Jan Roehrich Philipp Garbe 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-37293) ECS Agents are not deleted because Jenkins is unable to delete logs due to NFS locks
Title: Message Title Philipp Garbe closed an issue as Done No feedback since months Jenkins / JENKINS-37293 ECS Agents are not deleted because Jenkins is unable to delete logs due to NFS locks Change By: Philipp Garbe Status: Open Closed Resolution: Done 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-32740) Slaves which never connect due to ECS resource constraints never get removed
Title: Message Title Philipp Garbe closed an issue as Done No feedback since months Jenkins / JENKINS-32740 Slaves which never connect due to ECS resource constraints never get removed Change By: Philipp Garbe Status: Open Closed Resolution: Done 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-31197) New jobs are not creating a new container
Title: Message Title Philipp Garbe closed an issue as Done No feedback since months Jenkins / JENKINS-31197 New jobs are not creating a new container Change By: Philipp Garbe Status: Open Closed Resolution: Done 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.
