[JIRA] (JENKINS-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Evaristo Gutierrez updated JENKINS-54375 Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Change By: Evaristo Gutierrez Status: In Review 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Evaristo Gutierrez commented on JENKINS-54375 Re: Setup a release flow for Jenkinsfile Runner Reproduction steps: https://github.com/oleg-nenashev/ci.jenkins.io-runner/pull/20 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Evaristo Gutierrez updated JENKINS-54375 Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Change By: Evaristo Gutierrez Status: In Progress Review 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Isa Vilacides edited a comment on JENKINS-54375 Re: Setup a release flow for Jenkinsfile Runner Ensure Missing test: ensure that class loading happens from the bundle of Jenkins core and not from the version that Jenkinsfile runner provides 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Isa Vilacides commented on JENKINS-54375 Re: Setup a release flow for Jenkinsfile Runner Ensure that class loading happens from the bundle of Jenkins core and not from the version that Jenkinsfile runner provides 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Evaristo Gutierrez updated an issue Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Change By: Evaristo Gutierrez There is no official release flow for Jenkisnfile Runner, currently it's not uploaded to artifactory and jenkinsx is using a commit of the jenkinsfile runner. We need In some though in some cases a rebuild build from tag is required (e.g. Custom WAR Packager) and right now it's using a commit only commits can be used .This could be achieved by: * mvn release flow - up app assembler taget target directory needs to be zipped first to be used as the artifact. Also get permissions to publish in artifactory ** Example of ZIP packaging 1: [https://github.com/kibana-community/kibana4-static/blob/master/pom.xml]Acceptance criteria * Tags in github * Demos use tags instead of commit for CWP and Jenkinsfile runner * Changelog * Standard releases to Jenkins artifactory * The first BETA release is performed (1.0-beta-1) * Get permissions to publish in artifactory 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
[JIRA] (JENKINS-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Evaristo Gutierrez started work on JENKINS-54375 Change By: Evaristo Gutierrez 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Evaristo Gutierrez assigned an issue to Evaristo Gutierrez Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Change By: Evaristo Gutierrez Assignee: Evaristo Gutierrez 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Change By: Oleg Nenashev There is no official release flow for Jenkisnfile Runner, currently it's not uploaded to artifactory and jenkinsx is using a commit of the jenkinsfile runner. We need some though in some cases a rebuild from tag is required (e.g. Custom WAR Packager) and right now it's using a commit.This could be achieved by: * mvn release flow - up assembler taget directory needs to be zipped first to be used as the artifact. Also get permissions to publish in artifactory ** Example of ZIP packaging 1: [https://github.com/kibana-community/kibana4-static/blob/master/pom.xml] ** Example 2: Acceptance criteria * Tags in github * Demos use tags instead of commit for CWP and Jenkinsfile runner * Changelog * Standard releases to Jenkins artifactory * The first BETA release is performed (1.0-beta-1) 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Change By: Oleg Nenashev There is no official release flow for Jenkisnfile Runner, currently it's not uploaded to artifactory and jenkinsx is using a commit of the jenkinsfile runner. We need some though in some cases a rebuild from tag is required (e.g. Custom WAR Packager) and right now it's using a commit.This could be achieved by: * mvn release flow - up assembler taget directory needs to be zipped first to be used as the artifact. Also get permissions to publish in artifactory ** Example of ZIP packaging 1: [https://github.com/kibana-community/kibana4-static/blob/master/pom.xml] **Example 2: Acceptance criteria * Tags in github * Demos use tags instead of commit for CWP and Jenkinsfile runner * Changelog * Standard releases to Jenkins artifactory * The first release is performed (1.0-beta-1) 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Change By: Oleg Nenashev There is no official release flow for Jenkisnfile Runner, currently it's not uploaded to artifactory and jenkinsx is using a commit of the jenkinsfile runner. We need some though in some cases a rebuild from tag is required (e.g. Custom WAR Packager) and right now it's using a commit.This could be achieved by: * mvn release flow - up assembler taget directory needs to be zipped first to be used as the artifact. Also get permissions to publish in artifactory ** Example of ZIP packaging 1: [https://github.com/kibana-community/kibana4-static/blob/master/pom.xml] ** Acceptance criteria * Tags in github * Demos use tags instead of commit for CWP and Jenkinsfile runner * Changelog * Standard releases to Jenkins artifactory * The first release is performed (1.0-beta-1) 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Change By: Isa Vilacides There is no official release flow for Jenkisnfile Runner , currently it's not uploaded to artifactory and jenkinsx is using a commit of the jenkinsfile runner . We need some though in some cases a rebuild from tag is required (e.g. Custom WAR Packager) and right now it's using a commit . This could be achieved by: * mvn release flow - up assembler taget directory needs to be zipped first to be used as the artifact. Also get permissions to publish in artifactoryAcceptance criteria * Tags in github * Demos use tags instead of commit for CWP and Jenkinsfile runner * Changelog * Standard releases to Jenkins artifactory 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Change By: Oleg Nenashev There is no official release flow for Jenkisnfile Runner. We need some though in some cases a rebuild from tag is required (e . g. Custom WAR Packager). 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Issue Type: Task Assignee: Oleg Nenashev Components: jenkinsfile-runner Created: 2018-10-31 18:59 Priority: Minor Reporter: Oleg Nenashev There is no official release flow for Jenkisnfile Runner. We need some. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
