[JIRA] (JENKINS-55269) Provide a way to delete all used workspaces
Title: Message Title Ilya Lederman created an issue Jenkins / JENKINS-55269 Provide a way to delete all used workspaces Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2018-12-19 20:45 Priority: Minor Reporter: Ilya Lederman It would be great if there was an ability to clean all used workspaces at the end of the build. Currently, I use deleteDir as a post step, but some of my jobs have steps that run in parallel on separate nodes/workspaces. For that, I need to keep track of the stages that will use a separate workspace and I will have to add a post cleanup stage there as well. It would be great if we did not have to be very careful about each stages workspace and instead at the end of the build, delete all used workspaces. Add Comment
[JIRA] (JENKINS-53587) Sequential parallel stages show green while still running
Title: Message Title Ilya Lederman updated an issue Jenkins / JENKINS-53587 Sequential parallel stages show green while still running Change By: Ilya Lederman Summary: Sequential parallel stages show as green while still running 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-53587) Sequential parallel stages show as still running
Title: Message Title Ilya Lederman created an issue Jenkins / JENKINS-53587 Sequential parallel stages show as still running Issue Type: Bug Assignee: Unassigned Attachments: image-2018-09-14-13-20-29-471.png Components: blueocean-plugin Created: 2018-09-14 20:24 Environment: org.jenkins-ci.main:jenkins-war:2.121.1 org.jenkins-ci:crypto-util:1.1 commons-httpclient:commons-httpclient:3.1-jenkins-1 aopalliance:aopalliance:1.0 org.jenkins-ci.main:jenkins-core:2.121.1 org.kohsuke.stapler:stapler-jelly:1.254 com.google.inject:guice:4.0 org.jenkins-ci.modules:slave-installer:1.6 org.springframework:spring-dao:1.2.9 org.jenkins-ci.modules:instance-identity:2.1 org.jenkins-ci:constant-pool-scanner:1.2 org.connectbot.jbcrypt:jbcrypt:1.0.0 org.jenkins-ci.modules:ssh-cli-auth:1.4 org.ow2.asm:asm-commons:5.0.3 org.jenkins-ci:symbol-annotation:1.1 com.github.jnr:jnr-constants:0.9.8 org.jenkins-ci.modules:windows-slave-installer:1.9.2 commons-digester:commons-digester:2.1 commons-io:commons-io:2.4 org.kohsuke:trilead-putty-extension:1.2 commons-codec:commons-codec:1.9 net.sf.kxml:kxml2:2.3.0 org.kohsuke:libzfs:0.8 org.jenkins-ci.ui:jquery-detached:1.2 org.kohsuke.stapler:json-lib:2.4-jenkins-2 org.jvnet.robust-http-client:robust-http-client:1.2 org.ow2.asm:asm:5.0.3 net.java.sezpoz:sezpoz:1.12 org.kohsuke.stapler:stapler-adjunct-timeline:1.5 org.slf4j:log4j-over-slf4j:1.7.25 org.jenkins-ci:version-number:1.4 org.codehaus.groovy:groovy-all:2.4.11 org.jvnet.hudson:commons-jelly-tags-define:1.0.1-hudson-20071021 org.jenkins-ci:jmdns:3.4.0-jenkins-3 commons-lang:commons-lang:2.6 org.springframework:spring-jdbc:1.2.9 org.codehaus.woodstox:wstx-asl:3.2.9 org.springframework:spring-core:2.5.6.SEC03 org.springframework:spring-aop:2.5.6.SEC03 org.samba.jcifs:jcifs:1.3.17-kohsuke-1 org.jenkins-ci:bytecode-compatibility-transformer:1.8 org.apache.ant:ant:1.9.2 com.sun.solaris:embedded_su4j:1.1 javax.inject:javax.inject:1 org.jenkins-ci.modules:upstart-slave-installer:1.1 org.apache.commons:commons-compress:1.10 commons-beanutils:commons-beanutils:1.8.3 org.jvnet.localizer:localizer:1.24 org.fusesource.jansi:jansi:1.11 org.jenkins-ci.modules:sshd:2.4 org.springframework:spring-beans:2.5.6.SEC03 javax.xml.stream:stax-api:1.0-2 org.slf4j:slf4j-jdk14:1.7.25 org.jvnet.hudson:activation:1.1.1-hudson-1 org.jenkins-ci.main:cli:2.121.1 commons-jelly:commons-jelly-tags-fmt:1.0
[JIRA] (JENKINS-53501) Render sequential stages that are not in parallel
Title: Message Title
Ilya Lederman created an issue
Jenkins / JENKINS-53501
Render sequential stages that are not in parallel
Issue Type:
Improvement
Assignee:
Unassigned
Attachments:
image-2018-09-10-14-04-00-895.png
Components:
blueocean-plugin
Created:
2018-09-10 21:05
Priority:
Minor
Reporter:
Ilya Lederman
The new sequential stages improvement is awesome and I understand it's meant for use in parallel, but I do have a use case where I am not using it in parallel. Take this pipeline example for integration tests:
stage('Integration Tests') {
options {
lock('ci-instrument')
}
stages {
stage('Setup') {
agent {
label 'ci-instrument'
}
steps {
sh ''
}
stage('Run Tests') {
agent {
dockerfile {
}
}
steps {
sh 'NOT running on "ci-instrument", but it still needs to be locked"
}
}
stage('Copy results') {
}
}
}
This is visualized as It would be nice to have the Setup, Run Tests, and Copy Test Results stages to be under the Integration Tests stage, either always visible or maybe clicking Integration Tests will pop up the stages under it.
