February 2017 - jbosstools-issues

[JBoss JIRA] (JBTIS-1050) Move MWAE Jenkins jobs to Central CI

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1050?page=com.atlassian.jira.plugin... ] Paul Leacu updated JBTIS-1050: ------------------------------ Description: The middleware Jenkins jobs need to be migrated to Central CI https://mojo.redhat.com/groups/mw-qe-central-ci-migration ref: @lucinka >From Nick: I'm also working on a migrateJob.sh script which makes it easier to copy & modify a job so that migration isn't so manual a process. It generates a stub job on the CCI server based on a template, then downloads the config.xml and replaces it with the old job from Bos MW Jenkins. But before pushing it back to CCI, it applies some sed transforms to fix things like JDK name, Maven name, label expression / assignedNode (we don't have "RHEL6" or "RHEL7" on CCI, only rhel7 and "rhel7-devstudio-releng" slaves... plus some windows and OSX ones for ITests). It's not 100% working yet but it's better than doing the work by hand. https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/migrat... It requires that you compile and run my jenkins sync/publisher mojos [1],[2], which are wrapped with my hacky hud{push,pull}*.sh scripts (they're just simplifications to be able to push/pull job configs w/ less typing). So it's a bit of a kludge at the moment but I can walk you through set up if you're ready to start migrating. Or you can wait until I'm done.) [1] https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-sync-pl... [2] https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-publish... --- Work in progress: https://issues.jboss.org/browse/JBDS-4233 and http://etherpad.corp.redhat.com/nboldt-status MOJO doc: https://mojo.redhat.com/docs/DOC-1099087#comment-1053465 Central CI migration sync call on Wednesdays (every 4 weeks). I just go as fly on the wall. * Blue Jeans: https://bluejeans.com/327849748 * Meeting agenda/log: http://etherpad.corp.redhat.com/fb2t56DJnX * Mojo: https://mojo.redhat.com/groups/mw-qe-central-ci-migration * ML: mw-scale-ci(a)redhat.com was: The middleware Jenkins jobs need to be mograted to Central CI https://mojo.redhat.com/groups/mw-qe-central-ci-migration ref: @lucinka > Move MWAE Jenkins jobs to Central CI > ------------------------------------ > > Key: JBTIS-1050 > URL: https://issues.jboss.org/browse/JBTIS-1050 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > > The middleware Jenkins jobs need to be migrated to Central CI > https://mojo.redhat.com/groups/mw-qe-central-ci-migration > ref: @lucinka > From Nick: > I'm also working on a migrateJob.sh script which makes it easier to > copy & modify a job so that migration isn't so manual a process. > It generates a stub job on the CCI server based on a template, then > downloads the config.xml and replaces it with the old job from Bos MW > Jenkins. But before pushing it back to CCI, it applies some sed > transforms to fix things like JDK name, Maven name, label expression / > assignedNode (we don't have "RHEL6" or "RHEL7" on CCI, only rhel7 and > "rhel7-devstudio-releng" slaves... plus some windows and OSX ones for > ITests). It's not 100% working yet but it's better than doing the work > by hand. > https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/migrat... > It requires that you compile and run my jenkins sync/publisher mojos > [1],[2], which are wrapped with my hacky hud{push,pull}*.sh scripts > (they're just simplifications to be able to push/pull job configs w/ > less typing). So it's a bit of a kludge at the moment but I can walk > you through set up if you're ready to start migrating. Or you can wait > until I'm done.) > [1] https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-sync-pl... > [2] https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-publish... > --- > Work in progress: > https://issues.jboss.org/browse/JBDS-4233 and > http://etherpad.corp.redhat.com/nboldt-status > MOJO doc: > https://mojo.redhat.com/docs/DOC-1099087#comment-1053465 > Central CI migration sync call on Wednesdays (every 4 weeks). I just > go as fly on the wall. > * Blue Jeans: https://bluejeans.com/327849748 > * Meeting agenda/log: http://etherpad.corp.redhat.com/fb2t56DJnX > * Mojo: https://mojo.redhat.com/groups/mw-qe-central-ci-migration > * ML: mw-scale-ci(a)redhat.com -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4289) Update site page not updated to 10.3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4289?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4289 at 2/27/17 2:34 PM: ----------------------------------------------------------- Problem was a misconfiguration/bug in the https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... job, which updates the index.html and composite*.xml files as part of a release. Changes: * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... (or see https://github.com/jbdevstudio/jbdevstudio-ci/commits/master) * https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/afba5c2d1daa04ed... and https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/40ca5a16e7121c2e... I then ran the job's steps by hand and created these changes: * https://github.com/jbdevstudio/jbdevstudio-website/commit/1ba899bc666cb23... So now both the /development/ and /stable/ pages and update sites are up to date: * https://devstudio.jboss.com/10.0/development/updates/ * https://devstudio.jboss.com/10.0/stable/updates/ cc: [~mat.booth] FYI. was (Author: nickboldt): Problem was a misconfiguration/bug in the https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... job, which updates the index.html and composite*.xml files as part of a release. Changes: * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... (or see https://github.com/jbdevstudio/jbdevstudio-ci/commits/master) * https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/afba5c2d1daa04ed... and https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/40ca5a16e7121c2e... I then ran the job's steps by hand and created these changes: * https://github.com/jbdevstudio/jbdevstudio-website/commit/1ba899bc666cb23... So now both the /development/ and /stable/ pages and update sites are up to date: * https://devstudio.jboss.com/10.0/development/updates/ * https://devstudio.jboss.com/10.0/stable/updates/ > Update site page not updated to 10.3 > ------------------------------------ > > Key: JBDS-4289 > URL: https://issues.jboss.org/browse/JBDS-4289 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: updatesite > Affects Versions: 10.3.0.GA > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.3.0.GA > > Attachments: Stable_update_site_2017-02-27_09-43-17.png, Stable_update_site_2017-02-27_10-14-35.png > > > Stable update site (1) seems to be not updated to 10.3. They contain text "Latest Build: 10.2.0.GA" and links to Update site zip, Target platform zip, etc. are pointing to 10.2. > (1) https://devstudio.redhat.com/10.0/stable/updates/ > !Stable_update_site_2017-02-27_10-14-35.png|thumbnail! > Problem is probably only in html page, because when I try to install BYOE from (1) then I see that update site contains 10.3. > !Stable_update_site_2017-02-27_09-43-17.png|thumbnail! > The central and early access folders for 10.3.0.GA are missing in \[1\] and \[2\]. > \[1\] https://devstudio.redhat.com/10.0/stable/updates/discovery.central/ > \[2\] https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4289) Update site page not updated to 10.3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4289?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-4289. ------------------------------ Fix Version/s: 10.3.0.GA (was: 10.4.0.AM1) Resolution: Done > Update site page not updated to 10.3 > ------------------------------------ > > Key: JBDS-4289 > URL: https://issues.jboss.org/browse/JBDS-4289 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: updatesite > Affects Versions: 10.3.0.GA > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.3.0.GA > > Attachments: Stable_update_site_2017-02-27_09-43-17.png, Stable_update_site_2017-02-27_10-14-35.png > > > Stable update site (1) seems to be not updated to 10.3. They contain text "Latest Build: 10.2.0.GA" and links to Update site zip, Target platform zip, etc. are pointing to 10.2. > (1) https://devstudio.redhat.com/10.0/stable/updates/ > !Stable_update_site_2017-02-27_10-14-35.png|thumbnail! > Problem is probably only in html page, because when I try to install BYOE from (1) then I see that update site contains 10.3. > !Stable_update_site_2017-02-27_09-43-17.png|thumbnail! > The central and early access folders for 10.3.0.GA are missing in \[1\] and \[2\]. > \[1\] https://devstudio.redhat.com/10.0/stable/updates/discovery.central/ > \[2\] https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4289) Update site page not updated to 10.3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4289?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4289 at 2/27/17 2:32 PM: ----------------------------------------------------------- Problem was a misconfiguration/bug in the https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... job, which updates the index.html and composite*.xml files as part of a release. Changes: * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... (or see https://github.com/jbdevstudio/jbdevstudio-ci/commits/master) * https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/afba5c2d1daa04ed... and https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/40ca5a16e7121c2e... I then ran the job's steps by hand and created these changes: * https://github.com/jbdevstudio/jbdevstudio-website/commit/1ba899bc666cb23... So now both the /development/ and /stable/ pages and update sites are up to date: * https://devstudio.jboss.com/10.0/development/updates/ * https://devstudio.jboss.com/10.0/stable/updates/ was (Author: nickboldt): Problem was a misconfiguration/bug in the https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... job, which updates the index.html and composite*.xml files as part of a release. Changes: * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... (or see https://github.com/jbdevstudio/jbdevstudio-ci/commits/master) * https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/afba5c2d1daa04ed... and https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/40ca5a16e7121c2e... I then ran the job's steps by hand and created these changes: https://github.com/jbdevstudio/jbdevstudio-website/commit/1ba899bc666cb23... So now both the /development/ and /stable/ pages and update sites are up to date: * https://devstudio.jboss.com/10.0/development/updates/ * https://devstudio.jboss.com/10.0/stable/updates/ > Update site page not updated to 10.3 > ------------------------------------ > > Key: JBDS-4289 > URL: https://issues.jboss.org/browse/JBDS-4289 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: updatesite > Affects Versions: 10.3.0.GA > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.3.0.GA > > Attachments: Stable_update_site_2017-02-27_09-43-17.png, Stable_update_site_2017-02-27_10-14-35.png > > > Stable update site (1) seems to be not updated to 10.3. They contain text "Latest Build: 10.2.0.GA" and links to Update site zip, Target platform zip, etc. are pointing to 10.2. > (1) https://devstudio.redhat.com/10.0/stable/updates/ > !Stable_update_site_2017-02-27_10-14-35.png|thumbnail! > Problem is probably only in html page, because when I try to install BYOE from (1) then I see that update site contains 10.3. > !Stable_update_site_2017-02-27_09-43-17.png|thumbnail! > The central and early access folders for 10.3.0.GA are missing in \[1\] and \[2\]. > \[1\] https://devstudio.redhat.com/10.0/stable/updates/discovery.central/ > \[2\] https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4289) Update site page not updated to 10.3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4289?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4289: ---------------------------------- Problem was a misconfiguration/bug in the https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... job, which updates the index.html and composite*.xml files as part of a release. Changes: * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... (or see https://github.com/jbdevstudio/jbdevstudio-ci/commits/master) * https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/afba5c2d1daa04ed... and https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/40ca5a16e7121c2e... I then ran the job's steps by hand and created these changes: https://github.com/jbdevstudio/jbdevstudio-website/commit/1ba899bc666cb23... So now both the /development/ and /stable/ pages and update sites are up to date: * https://devstudio.jboss.com/10.0/development/updates/ * https://devstudio.jboss.com/10.0/stable/updates/ > Update site page not updated to 10.3 > ------------------------------------ > > Key: JBDS-4289 > URL: https://issues.jboss.org/browse/JBDS-4289 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: updatesite > Affects Versions: 10.3.0.GA > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.4.0.AM1 > > Attachments: Stable_update_site_2017-02-27_09-43-17.png, Stable_update_site_2017-02-27_10-14-35.png > > > Stable update site (1) seems to be not updated to 10.3. They contain text "Latest Build: 10.2.0.GA" and links to Update site zip, Target platform zip, etc. are pointing to 10.2. > (1) https://devstudio.redhat.com/10.0/stable/updates/ > !Stable_update_site_2017-02-27_10-14-35.png|thumbnail! > Problem is probably only in html page, because when I try to install BYOE from (1) then I see that update site contains 10.3. > !Stable_update_site_2017-02-27_09-43-17.png|thumbnail! > The central and early access folders for 10.3.0.GA are missing in \[1\] and \[2\]. > \[1\] https://devstudio.redhat.com/10.0/stable/updates/discovery.central/ > \[2\] https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23975) Aerogear New and Noteworthy for 4.4.3.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23975?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23975: ------------------------------- Fix Version/s: 4.4.3.Final > Aerogear New and Noteworthy for 4.4.3.Final > ----------------------------------------------------- > > Key: JBIDE-23975 > URL: https://issues.jboss.org/browse/JBIDE-23975 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Jeff MAURY > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.4.3.Final > > > Gorkem Ercan, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Aerogear JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Aerogear, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Aerogear by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-23968 #comment Create N&N for Aerogear 4.4.3.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Aerogear for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.3.Final since the AM3 release of Aerogear, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.3.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.3.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23981) Central New and Noteworthy for 4.4.3.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23981?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23981: ------------------------------- Fix Version/s: 4.4.3.Final > Central New and Noteworthy for 4.4.3.Final > ----------------------------------------------------- > > Key: JBIDE-23981 > URL: https://issues.jboss.org/browse/JBIDE-23981 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Jeff MAURY > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.4.3.Final > > > Fred Bricon, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Central JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Central, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Central by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-23968 #comment Create N&N for Central 4.4.3.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Central for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.3.Final since the AM3 release of Central, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.3.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.3.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23869: ------------------------------------ This is an upstream problem. The JSON payload is generated by OpenShift (because you're not authorized) and assumes the status field is always an integer. I opened an upstream issue. > ClassCastException with Jolokia connection > ------------------------------------------ > > Key: JBIDE-23869 > URL: https://issues.jboss.org/browse/JBIDE-23869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, openshift > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: jmx, jolokia, openshift > Fix For: 4.4.4.AM1 > > Attachments: image-2017-02-06-13-54-27-708.png > > > !image-2017-02-06-13-54-27-708.png|thumbnail! > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long > at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58) > at org.jolokia.client.J4pClient.execute(J4pClient.java:195) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1050) Move MWAE Jenkins jobs to Central CI

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1050?page=com.atlassian.jira.plugin... ] Paul Leacu updated JBTIS-1050: ------------------------------ Description: The middleware Jenkins jobs need to be mograted to Central CI https://mojo.redhat.com/groups/mw-qe-central-ci-migration ref: @lucinka was: The middleware Jenkins jobs need to be mograted to Central CI https://mojo.redhat.com/groups/mw-qe-central-ci-migration > Move MWAE Jenkins jobs to Central CI > ------------------------------------ > > Key: JBTIS-1050 > URL: https://issues.jboss.org/browse/JBTIS-1050 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > > The middleware Jenkins jobs need to be mograted to Central CI > https://mojo.redhat.com/groups/mw-qe-central-ci-migration > ref: @lucinka -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1050) Move MWAE Jenkins jobs to Central CI

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1050?page=com.atlassian.jira.plugin... ] Paul Leacu updated JBTIS-1050: ------------------------------ Description: The middleware Jenkins jobs need to be mograted to Central CI https://mojo.redhat.com/groups/mw-qe-central-ci-migration was:The middleware Jenkins jobs need to be mograted to Central CI > Move MWAE Jenkins jobs to Central CI > ------------------------------------ > > Key: JBTIS-1050 > URL: https://issues.jboss.org/browse/JBTIS-1050 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > > The middleware Jenkins jobs need to be mograted to Central CI > https://mojo.redhat.com/groups/mw-qe-central-ci-migration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2017