March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24112) document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24112?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-24112: --------------------------------------------- When I configured the bot a while ago i deliberately did not give it any kind of access beyond creating issues since then if it went errand it could at most only delete its own issues. I don't know what you are looking for to have assigned - but one of the benefits/sideeffects of having it configured so those who are component owners get notified about jiralint is that component owners will see issues. So not sure what is trying to be solved with assigning to sepcific users - but if needed the minimum would to grant the bot committer status - but then it can actually do "damage" so just be aware of that. I would recommend using a different bot for that though. > document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide > --------------------------------------------------------------------------------------- > > Key: JBIDE-24112 > URL: https://issues.jboss.org/browse/JBIDE-24112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2 > > Attachments: jiralint.user.no.perms.to.assign.txt > > > Need to document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide. Also can create a job in jenkins to wrap the creation of the N&N JIRAs so heir creation is less error-prone. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4288) 'Rename artifacts to remove timestamp and buildID' should be a jenkins job, not manual step

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4288?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-4288. ------------------------------ Resolution: Done > 'Rename artifacts to remove timestamp and buildID' should be a jenkins job, not manual step > ------------------------------------------------------------------------------------------- > > Key: JBDS-4288 > URL: https://issues.jboss.org/browse/JBDS-4288 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.3.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.4.0.AM2 > > > In https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... there's a step that's done manually on dev01. This should be replaced by a job so it can be part of the pipeline. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4288) 'Rename artifacts to remove timestamp and buildID' should be a jenkins job, not manual step

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4288?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4288: ----------------------------- Fix Version/s: 10.4.0.AM2 (was: 10.4.0.AM3) > 'Rename artifacts to remove timestamp and buildID' should be a jenkins job, not manual step > ------------------------------------------------------------------------------------------- > > Key: JBDS-4288 > URL: https://issues.jboss.org/browse/JBDS-4288 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.3.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.4.0.AM2 > > > In https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... there's a step that's done manually on dev01. This should be replaced by a job so it can be part of the pipeline. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4288) 'Rename artifacts to remove timestamp and buildID' should be a jenkins job, not manual step

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4288?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4288: ---------------------------------- Job created: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... Doc updated: https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/9e68841fc06348fa... > 'Rename artifacts to remove timestamp and buildID' should be a jenkins job, not manual step > ------------------------------------------------------------------------------------------- > > Key: JBDS-4288 > URL: https://issues.jboss.org/browse/JBDS-4288 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.3.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.4.0.AM3 > > > In https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... there's a step that's done manually on dev01. This should be replaced by a job so it can be part of the pipeline. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24112) document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24112?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24112: ------------------------------- Attachment: jiralint.user.no.perms.to.assign.txt > document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide > --------------------------------------------------------------------------------------- > > Key: JBIDE-24112 > URL: https://issues.jboss.org/browse/JBIDE-24112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2 > > Attachments: jiralint.user.no.perms.to.assign.txt > > > Need to document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide. Also can create a job in jenkins to wrap the creation of the N&N JIRAs so heir creation is less error-prone. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24112) document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24112?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24112 at 3/16/17 4:08 PM: ------------------------------------------------------------- The pre-release and pre-staging steps have now been documented, and there's a new job you can use to generate a reminder email about creation of N&N JIRAs. Unfortunately, since the jiralint machine user can't assign issues to people, we can't run the job to do the work automatically - so it generates an email with instructions instead. Perhaps we SHOULD grant access to the jiralint machine user so that we can use it to do more automatically? This would also include the JIRAs created for root pom [1] and branching updates [2], which could be further simplified & automated. [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [~maxandersen] [~jeffmaury] WDYT? Is it safe to give JIRALINT permission to assign JIRAs to users? Can that be done without making it an administrator? was (Author: nickboldt): The pre-release and pre-staging steps have now been documented, and there's a new job you can use to generate a reminder email about creation of N&N JIRAs. Unfortunately, since the jiralint machine user can't assign issues to people, we can't run the job to do the work automatically. Perhaps we SHOULD grant admin access to the machine user so that we can use it to do more automatically? This would also include the JIRAs created for root pom and branching updates, which could be further simplified. [~maxandersen] [~jeffmaury] WDYT? Is it safe to give JIRALINT permission to assign JIRAs to users? Can that be done without making it an administrator? > document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide > --------------------------------------------------------------------------------------- > > Key: JBIDE-24112 > URL: https://issues.jboss.org/browse/JBIDE-24112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2 > > > Need to document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide. Also can create a job in jenkins to wrap the creation of the N&N JIRAs so heir creation is less error-prone. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24112) document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24112?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24112 at 3/16/17 4:08 PM: ------------------------------------------------------------- The pre-release and pre-staging steps have now been documented, and there's a new job you can use to generate a reminder email about creation of N&N JIRAs. Unfortunately, since the jiralint machine user can't assign issues to people, we can't run the job to do the work automatically - so it generates an email with instructions instead. Perhaps we SHOULD grant access to the jiralint machine user so that we can use it to do more automatically? This would also include the JIRAs created for root pom [1] and branching updates [2], which could be further simplified & automated. [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [~maxandersen] [~jeffmaury] WDYT? Is it safe to give *jiralint* machine user permission to assign JIRAs to users? Can that be done without making it an administrator? was (Author: nickboldt): The pre-release and pre-staging steps have now been documented, and there's a new job you can use to generate a reminder email about creation of N&N JIRAs. Unfortunately, since the jiralint machine user can't assign issues to people, we can't run the job to do the work automatically - so it generates an email with instructions instead. Perhaps we SHOULD grant access to the jiralint machine user so that we can use it to do more automatically? This would also include the JIRAs created for root pom [1] and branching updates [2], which could be further simplified & automated. [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [~maxandersen] [~jeffmaury] WDYT? Is it safe to give JIRALINT permission to assign JIRAs to users? Can that be done without making it an administrator? > document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide > --------------------------------------------------------------------------------------- > > Key: JBIDE-24112 > URL: https://issues.jboss.org/browse/JBIDE-24112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2 > > > Need to document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide. Also can create a job in jenkins to wrap the creation of the N&N JIRAs so heir creation is less error-prone. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24112) document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24112?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-24112. -------------------------------- Resolution: Done The pre-release and pre-staging steps have now been documented, and there's a new job you can use to generate a reminder email about creation of N&N JIRAs. Unfortunately, since the jiralint machine user can't assign issues to people, we can't run the job to do the work automatically. Perhaps we SHOULD grant admin access to the machine user so that we can use it to do more automatically? This would also include the JIRAs created for root pom and branching updates, which could be further simplified. [~maxandersen] [~jeffmaury] WDYT? Is it safe to give JIRALINT permission to assign JIRAs to users? Can that be done without making it an administrator? > document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide > --------------------------------------------------------------------------------------- > > Key: JBIDE-24112 > URL: https://issues.jboss.org/browse/JBIDE-24112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2 > > > Need to document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide. Also can create a job in jenkins to wrap the creation of the N&N JIRAs so heir creation is less error-prone. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24112) document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24112?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24112: ------------------------------------ New doc: https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... New job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide > --------------------------------------------------------------------------------------- > > Key: JBIDE-24112 > URL: https://issues.jboss.org/browse/JBIDE-24112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2 > > > Need to document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide. Also can create a job in jenkins to wrap the creation of the N&N JIRAs so heir creation is less error-prone. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4313) Show Installer window when content is loaded and ready

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4313?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4313: -------------------------------- Description: When installer starts it shows installer's window right away and then loads application url into it. That reveals 'UI cooking process' to the user. Installer's UI is implemented as AngularJS application and it takes considerable time to load. Depending on user's workstation performance it might take no time or several seconds. During that time window screen just stays blank. Below are demos how it worked before and after !DevSuite Installer-Window Loading Before.mp4! !DevSuite Installer-Window Loading After.mp4! was: When installer starts it shows installer's window right away and then loads application url into it. That reveals 'UI cooking process' to the user. Installer's UI is implemented as AngularJS application and it takes considerable time to load. Depending on user's workstation performance it might take no time or several seconds. During that time window screen just stays blank. !DevSuite Installer-Window Loading Before.mp4! !DevSuite Installer-Window Loading After.mp4! > Show Installer window when content is loaded and ready > ------------------------------------------------------ > > Key: JBDS-4313 > URL: https://issues.jboss.org/browse/JBDS-4313 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy, Sprint_Demo > Fix For: 10.4.0.AM2 > > Attachments: DevSuite Installer-Window Loading After.mp4, DevSuite Installer-Window Loading Before.mp4 > > > When installer starts it shows installer's window right away and then loads application url into it. That reveals 'UI cooking process' to the user. Installer's UI is implemented as AngularJS application and it takes considerable time to load. Depending on user's workstation performance it might take no time or several seconds. During that time window screen just stays blank. > Below are demos how it worked before and after > !DevSuite Installer-Window Loading Before.mp4! !DevSuite Installer-Window Loading After.mp4! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 March 2017