[JBoss JIRA] (JBIDE-24015) Add Mockito for Docker Integration tests
by Josef Kopriva (JIRA)
Josef Kopriva created JBIDE-24015:
-------------------------------------
Summary: Add Mockito for Docker Integration tests
Key: JBIDE-24015
URL: https://issues.jboss.org/browse/JBIDE-24015
Project: Tools (JBoss Tools)
Issue Type: Task
Components: integration-tests
Affects Versions: 4.4.4.AM1
Reporter: Josef Kopriva
Add Mockito to Docker integration tests to run integration tests on eclipse slaves.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23975) Aerogear New and Noteworthy for 4.4.3.Final
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23975?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-23975.
------------------------------
Resolution: Rejected
> 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)
8 years, 8 months
[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)
8 years, 8 months