[JIRA] (JENKINS-61027) Add option to pass parameters/environment values from multibranch to triggered jobs
Title: Message Title Aytunc BEKEN closed an issue as Won't Do Jenkins / JENKINS-61027 Add option to pass parameters/environment values from multibranch to triggered jobs Change By: Aytunc BEKEN Status: Open Closed Resolution: Won't Do 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.204500.1581324478000.1855.1585402500502%40Atlassian.JIRA.
[JIRA] (JENKINS-61027) Add option to pass parameters/environment values from multibranch to triggered jobs
Title: Message Title Aytunc BEKEN edited a comment on JENKINS-61027 Re: Add option to pass parameters/environment values from multibranch to triggered jobs I thought about this, However, the way that I implemented triggering jobs do not make it possible to parse Jenkins file of multibranch job. Sorry for the inconvenience. 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.204500.1581324478000.1852.1585402500423%40Atlassian.JIRA.
[JIRA] (JENKINS-61027) Add option to pass parameters/environment values from multibranch to triggered jobs
Title: Message Title Aytunc BEKEN commented on JENKINS-61027 Re: Add option to pass parameters/environment values from multibranch to triggered jobs I thought about this, However, the way that I implemented triggering jobs do not make it possible to parse Jenkins file of multibranch job. 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.204500.1581324478000.1849.1585402380189%40Atlassian.JIRA.
[JIRA] (JENKINS-61027) Add option to pass parameters/environment values from multibranch to triggered jobs
Title: Message Title Aytunc BEKEN assigned an issue to Aytunc BEKEN Jenkins / JENKINS-61027 Add option to pass parameters/environment values from multibranch to triggered jobs Change By: Aytunc BEKEN Assignee: Aytunc BEKEN 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.204500.1581324478000.5252.1581325080468%40Atlassian.JIRA.
[JIRA] (JENKINS-61027) Add option to pass parameters/environment values from multibranch to triggered jobs
Title: Message Title Oguzhan Uysal created an issue Jenkins / JENKINS-61027 Add option to pass parameters/environment values from multibranch to triggered jobs Issue Type: Bug Assignee: Unassigned Components: multibranch-action-triggers-plugin Created: 2020-02-10 08:47 Environment: multibranch-action-trigger-plugin v1.8 Priority: Minor Reporter: Oguzhan Uysal We have one or more multibranch pipelines which uses declarative jenkinsfile to build, puch & deploy docker images. Our wish is to do some garbage collection and delete these images and deployments when a branch/pipeline is deleted. Depending on our branching strategy we decide if a deployment takes place and we sanitise tags to comply with docker and kubernetes naming schemes. Because of this we assign dynamic values to the build context's environment variables/parameters and wish to pass these values to the triggered job for cleanup. Add Comment
