June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21657: ---------------------------------------- Sprint: devex #115 May 2016, devex #116 June 2016 (was: devex #115 May 2016) > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.x > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20904) automate publishing latest CI build to staging, then from staging to development (or stable)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-20904: ---------------------------------------- Sprint: devex #115 May 2016, devex #116 June 2016 (was: devex #115 May 2016) > automate publishing latest CI build to staging, then from staging to development (or stable) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-20904 > URL: https://issues.jboss.org/browse/JBIDE-20904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > Suggestion: > rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed. > So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion. > [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... > Examples of using a series of commands in parallel w/ a wait at the end: > http://stackoverflow.com/questions/19543139/bash-script-processing-comman... > {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code} > echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $# > {code} > More discussion: > {quote} > [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions > [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just: > * add && after the 1st rsync in each loop > * add & after the last one > * put a wait after the last loop > * give the big piece of code to procede directly to bash > {quote} > After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template. > And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job. > Scary, but much faster! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16158) Investigate tools/processes to templatize CI jobs

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16158?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16158: ---------------------------------------- Sprint: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015, devex #115 May 2016, devex #116 June 2016 (was: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015, devex #115 May 2016) > Investigate tools/processes to templatize CI jobs > ------------------------------------------------- > > Key: JBIDE-16158 > URL: https://issues.jboss.org/browse/JBIDE-16158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.x > > Attachments: devstudio.product_master_diff_generated_vs_server_copy.diff > > > Found something a bit more complete than the maven plugin - haven't tried it yet but its examples looks extremely clean. > python script for creating jobs (linked to puppet but can be used standalone) > http://ci.openstack.org/jenkins-job-builder/installation.html > Example: https://github.com/adaptivelab/jenkins-build/blob/develop/template.yaml > Article: http://techs.enovance.com/6006/manage-jenkins-jobs-with-yaml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22229) Tooling to check if patches/PRs are applied across both master and maintenance

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22229?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-22229: ---------------------------------------- Sprint: devex #115 May 2016, devex #116 June 2016 (was: devex #115 May 2016) > Tooling to check if patches/PRs are applied across both master and maintenance > ------------------------------------------------------------------------------ > > Key: JBIDE-22229 > URL: https://issues.jboss.org/browse/JBIDE-22229 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > 1. review and push https://github.com/jbosstools/jbosstools-build-ci/pull/143 > 2. migrate scripts in jbdevstudio-ci that also use python to generate JIRAs to the same repo > 3. externalize shared JIRA component mapping table so both scripts can use it -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22473) Environment Var Wizard: Cannot remove env vars

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22473?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22473: ------------------------------------------ [~scabanovich] I dont fully get why we should show deleted env variables? What makes you show them? !deleted-env-var.png! IMHO it's a bit strange if you can then "Edit.." them (which makes me go "humm..."). The result is consistent but not fully expected though: you get a new env var ("you think twice and you go aaahhh..."). > Environment Var Wizard: Cannot remove env vars > ---------------------------------------------- > > Key: JBIDE-22473 > URL: https://issues.jboss.org/browse/JBIDE-22473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: env_var_wizard, openshift_v3 > Fix For: 4.4.1.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22473) Environment Var Wizard: Cannot remove env vars

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22473?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22473: ------------------------------------- Attachment: deleted-env-var.png > Environment Var Wizard: Cannot remove env vars > ---------------------------------------------- > > Key: JBIDE-22473 > URL: https://issues.jboss.org/browse/JBIDE-22473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: env_var_wizard, openshift_v3 > Fix For: 4.4.1.Alpha1 > > Attachments: deleted-env-var.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22367) Create and use Neon.0.RC4a target platform

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22367?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-22367. ------------------------------- Closing as done. > Create and use Neon.0.RC4a target platform > ------------------------------------------ > > Key: JBIDE-22367 > URL: https://issues.jboss.org/browse/JBIDE-22367 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Labels: respin-a > Fix For: 4.4.0.Final > > > Prepare TP to use Neon.0.RC4 bits, which will be available June 9/10. Cloned from JBIDE-22200. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * update install/matrix jobs to use new Eclipse JEE/platform binary; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3608) update devstudio.redhat.com branding for DevStudio 10

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3608?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3608. ----------------------------- Verifying the change and closing. > update devstudio.redhat.com branding for DevStudio 10 > ----------------------------------------------------- > > Key: JBDS-3608 > URL: https://issues.jboss.org/browse/JBDS-3608 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer, website > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-b > Fix For: 10.0.0.GA > > > update branding for developers.redhat.com -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3606) update branding for devstudio 10.0 installer

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3606?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3606. ----------------------------- Verified in 10.0.0.GA-v20160615-1853-B33. > update branding for devstudio 10.0 installer > -------------------------------------------- > > Key: JBDS-3606 > URL: https://issues.jboss.org/browse/JBDS-3606 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Labels: respin-b > Fix For: 10.0.0.GA > > Attachments: installer-10.png > > > name and branding of JBDS set to change. Need the base izpack based installer to have an updated look. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3609) update splashscreen, about gfx, start icon for developers.redhat.com

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3609?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3609. ----------------------------- Verified in 10.0.0.GA-v20160615-1853-B33. > update splashscreen, about gfx, start icon for developers.redhat.com > -------------------------------------------------------------------- > > Key: JBDS-3609 > URL: https://issues.jboss.org/browse/JBDS-3609 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-b > Fix For: 10.0.0.GA > > Attachments: 3609_06152016_112229.png, 3609_06152016_112343.png, 3609_06152016_112445.png, 3609_06152016_112757.png, about-jbds10.png, devstudio_assets_revised.zip, launcher-icons-jbds10.png, splash-jbds10.png > > > update splashscreen, about gfx, start icon for developers.redhat.com -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 June 2016