[JIRA] (JENKINS-54605) Default stage for post section
Title: Message Title Kamil Grabowski commented on JENKINS-54605 Re: Default stage for post section Andrew Bayer thenk you 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-54605) Default stage for post section
Title: Message Title
Kamil Grabowski created an issue
Jenkins / JENKINS-54605
Default stage for post section
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-11-13 12:45
Environment:
Jenkins ver. 2.138.2 Pipeline: Model API 1.3.2
Priority:
Minor
Reporter:
Kamil Grabowski
At the moment all pipeline post steps will be displayed in the latest defined stage. For example:
pipeline {
agent;
stages {
stage('first stage') { ... }
stage('last stage') { ... }
}
post {
always { echo 'Hello World' }
}
}
The echo step will be assigned to the "last stage". Would be nice to have a new, "virtual" stage e.g. ("post actions") for all that things.
[JIRA] (JENKINS-54602) Pipeline post action should support conditions
Title: Message Title
Kamil Grabowski created an issue
Jenkins / JENKINS-54602
Pipeline post action should support conditions
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-11-13 11:16
Environment:
Jenkins ver. 2.138.2 Pipeline: Model API 1.3.2
Priority:
Minor
Reporter:
Kamil Grabowski
Hello, Would be nice to add a when conditions to pipeline post actions. Here is an example:
pipeline {
agent any;
stages { ... }
// run only for master branch
post {
when { branch 'master' }
failure {
// send slack notification about failure build
}
}
// run without any additional conditions (it works now)
post {
success { ... }
cleanup { ... }
}
}
I don't have a good idea how to implement this without breaking-changes. In this example there is an idea that we can add multiple pipeline post blocks (one for every when condition) Motivation: I would like to send notification about failed builds, but only for releases braches. We don't want to receive notifications about failed pull requests builds.
[JIRA] (JENKINS-54127) Add new option to pipeline - sshagent
Title: Message Title Kamil Grabowski updated an issue Jenkins / JENKINS-54127 Add new option to pipeline - sshagent Change By: Kamil Grabowski Component/s: ssh-agent-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-54127) Add new option to pipeline - sshagent
Title: Message Title
Kamil Grabowski created an issue
Jenkins / JENKINS-54127
Add new option to pipeline - sshagent
Issue Type:
Improvement
Assignee:
Unassigned
Components:
pipeline
Created:
2018-10-17 11:38
Priority:
Minor
Reporter:
Kamil Grabowski
Would be nice to be able to define sshagent as an option for stage or global pipeline. Here are examples:
// Global option
pipeline {
options {
sshagent('credential-id')
}
stages {
stage('ssh-deploy') {
steps {
sh 'ssh user@host command'
}
}
}
// option for single stage
pipeline {
stages {
stage('ssh-deploy') {
options {
sshagent('credential-id')
}
steps {
sh 'ssh user@host command'
}
}
}
}
// option for single stage + docker
pipeline {
stages {
stage('ssh-deploy') {
agent {
docker { image 'ubuntu:16.04' }
}
options {
sshagent('credential-id')
}
steps {
sh 'ssh user@host command'
}
}
}
}
[JIRA] (JENKINS-42612) Jenkins unable to find mvn command
Title: Message Title Kamil Grabowski assigned an issue to Unassigned Jenkins / JENKINS-42612 Jenkins unable to find mvn command Change By: Kamil Grabowski Assignee: Kamil Grabowski 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-42612) Jenkins unable to find mvn command
Title: Message Title Kamil Grabowski assigned an issue to Kamil Grabowski Jenkins / JENKINS-42612 Jenkins unable to find mvn command Change By: Kamil Grabowski Assignee: Kamil Grabowski 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-40698) Build is not triggered whether repo owner is lowercase
Title: Message Title Kamil Grabowski updated an issue Jenkins / JENKINS-40698 Build is not triggered whether repo owner is lowercase Change By: Kamil Grabowski I have a github organization named: MyOrganization and repository MyOrganization/my-repository.If I put "myorganization" (instead of "MyOrganization") as a GitHub Organization Owner then build is not triggered when one creates new pull request or a new commit .Build is triggered when I will run manually "Re-scan Organization". I think that github organization owner should be case insensitive. 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-40698) Build is not triggered whether repo owner is lowercase
Title: Message Title Kamil Grabowski updated an issue Jenkins / JENKINS-40698 Build is not triggered whether repo owner is lowercase Change By: Kamil Grabowski I have an a github organization named: MyOrganization and repository MyOrganization/my-repository.If I put "myorganization" (instead of "MyOrganization") as a GitHub Organization Owner then build is not triggered when one creates pull request.Build is triggered when I will run manually "Re-scan Organization". I think that github organization owner should be case insensitive. 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-40698) Build is not triggered whether repo owner is lowercase
Title: Message Title Kamil Grabowski created an issue Jenkins / JENKINS-40698 Build is not triggered whether repo owner is lowercase Issue Type: Bug Assignee: ben patterson Attachments: Screen Shot 2016-12-27 at 22.58.58.png Components: ghprb-plugin Created: 2016/Dec/27 10:04 PM Environment: Ubuntu Linux 14.04 64-bit Jenkins 2.38 Github Pull Request Builder 1.33.4 Priority: Minor Reporter: Kamil Grabowski I have an github organization named: MyOrganization and repository MyOrganization/my-repository. If I put "myorganization" (instead of "MyOrganization") as a GitHub Organization Owner then build is not triggered when one creates pull request. Build is triggered when I will run manually "Re-scan Organization". I think that github organization owner should be case insensitive. Add Comment
