Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JBTM-2481] Create WildFly component upgrade issue with JIRA update script #927

Merged

Conversation

gytis
Copy link
Contributor

@gytis gytis commented Oct 9, 2015

@jbosstm-bot
Copy link

Started testing this pull request with BLACKTIE profile on Windows: http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/981/

@jbosstm-bot
Copy link

BLACKTIE profile tests passed on Windows - Job complete http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/981/

@tomjenkinson
Copy link
Contributor

Looking good - but do we have some way to test this?

@gytis
Copy link
Contributor Author

gytis commented Oct 12, 2015

I did test it on Blacktie JIRA. Nothing automated for now. But I'll start
looking into introducing normal automated tests for them.

On Mon, Oct 12, 2015 at 1:28 PM, Tom Jenkinson notifications@github.com
wrote:

Looking good - but do we have some way to test this?


Reply to this email directly or view it on GitHub
#927 (comment).

@tomjenkinson
Copy link
Contributor

For the record, can you provide a link to the BLACKTIE issue that it created then please? I will review that issue to make sure it has the content we expect

@gytis
Copy link
Contributor Author

gytis commented Oct 12, 2015

https://issues.jboss.org/browse/BLACKTIE-457
It doesn't have fix version on purpose. I wasn't sure if we want to add
that, since they change quite frequently.

Also, I've just noticed that component is not there, but it should be. I'll
add that before merging.

On Mon, Oct 12, 2015 at 1:47 PM, Tom Jenkinson notifications@github.com
wrote:

For the record, can you provide a link to the BLACKTIE issue that it
created then please? I will review that issue to make sure it has the
content we expect


Reply to this email directly or view it on GitHub
#927 (comment).

@tomjenkinson
Copy link
Contributor

Thanks, and did the output print out the link to the new jira? Might be worth including the output from the console?

@gytis
Copy link
Contributor Author

gytis commented Oct 12, 2015

It does add the link to the new jira

On Mon, Oct 12, 2015 at 3:11 PM, Tom Jenkinson notifications@github.com
wrote:

Thanks, and did the output print out the link to the new jira? Might be
worth including the output from the console?


Reply to this email directly or view it on GitHub
#927 (comment).

@gytis gytis force-pushed the master-JBTM-2481-script-to-create-upstream-jira branch from fe3d503 to 00e88e4 Compare October 13, 2015 10:42
@gytis gytis merged commit 00e88e4 into jbosstm:master Oct 13, 2015
@gytis gytis deleted the master-JBTM-2481-script-to-create-upstream-jira branch October 13, 2015 10:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants