Skip to content

Conversation

@AnneTheAgile
Copy link

Usually I like the console log to be the most complete source of truth. Adding logging of the hockey result urls to the console log takes me a step closer to that.


int appIndex = applications.indexOf(application);

logger.println("HOCKEYAPP_INSTALL_URL" + installUrl);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The catch with putting this outside the if block on line 316, is that even though the value is available it might not be set in the environment data. Would this cause confusion?

Copy link
Author

@AnneTheAgile AnneTheAgile Sep 11, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you for reviewing!!! I think you meant line 361 not 316 ? ie this : https://github.com/AnneTheAgile/hockeyapp-plugin/blob/f55ab778243a04de69d51fefcbfdab8d802db392/src/main/java/hockeyapp/HockeyappRecorder.java#L361
I don't see that envData is ever set at all. Am I missing something?

My preference is regardless of what future code wants, ie what usages occur of environment variables, that the log indicates what it does since it does create links in the html for the build. Those links are not available by scraping the console log, but that is what I would like to do.
https://github.com/ohoeltke/hockeyapp-plugin/search?q=envdata&type=Code&utf8=%E2%9C%93

//update ; hmm, that search is not accurate. We can't search in forks, and the jenkinsci repo is a fork. so unless merge backs are done to ohoeltke/hockeyapp-plugin , then there is no search... and the last of ohoeltke/hockeyapp-plugin was 2012, so there were no merge backs. Ugh.
//update2; Search/Find in sublime shows it does not exist in this plugin. So it apparently only exists in the calling stuffs, which are what is responsible for creating left nav url links.
I'm not sure what code that is?
But regardless, this particular plugin would not need to mind about that, since it never minded the contents of envData previously.

@AnneTheAgile
Copy link
Author

Commented on @Brantone 's review.

@AnneTheAgile
Copy link
Author

@Brantone what do you think of my response?

…-doc-urls-in-log-170606

# Conflicts:
#	src/main/java/hockeyapp/HockeyappRecorder.java
@mezpahlan
Copy link

Hi @AnneTheAgile, thanks so much for this enhancement. Apologies it has taken so long to get around to reviewing it. The master branch in the upstream repository has moved on quite a bit so I've updated this PR to take that into account. In doing this I have had to re-implement your changes due to a merge conflict. Could you take a look and let me know if they are still what you are expecting?

I'll mark them up with some small comments. Many thanks.


if (appIndex == 0) {
envData.add("HOCKEYAPP_CONFIG_URL", configUrl);
logger.println("HOCKEYAPP_CONFIG_URL" + configUrl);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you double check that this is what you want to see in the log console output? It will look something like:

HOCKEYAPP_CONFIG_URL:http://your.url.to.config/

Would it be better to do something like:

logger.println("HOCKEYAPP_CONFIG_URL: " + configUrl);

So that it will output as (note the spaces and colon):

HOCKEYAPP_CONFIG_URL: http://your.url.to.config/

}

envData.add("HOCKEYAPP_CONFIG_URL_" + appIndex, configUrl);
logger.println("HOCKEYAPP_CONFIG_URL_" + appIndex + ": " + configUrl);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can have multiple config (and install) urls returned from HockeyApp. As with the environment data object we expose all urls that we are able to. Do you still want to do that with your change in the console logger? If so you can keep this and the equivalent one for installation links below. Otherwise if you just want the first configuration url feel free to delete these lines....... but I suspect you probably want them too ;).

Copy link

@mezpahlan mezpahlan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added two comments for minor changes. Let me know if you are happy with the suggestions and either you or I can implement them.

@AnneTheAgile
Copy link
Author

@mezpahlan ty so much for fixing this! Yes please I am very happy, I look forward to the next release.
Thank you for taking on maintainer role :)

@douglasknudsen
Copy link

douglasknudsen commented Sep 25, 2018 via email

@mezpahlan
Copy link

mezpahlan commented Sep 25, 2018

Quite possibly #42 undid something from #46 . Too difficult to check that on my mobile but will pick this up at home.

This PR is still in review and I don't think related to your issue so if you don't mind I'll pick this backup on #46 which was your original issue I believe and the one that you've spotted a regression in.

@douglasknudsen
Copy link

douglasknudsen commented Sep 25, 2018 via email

@douglasknudsen
Copy link

sorry for carrying this on in this thread...got the emails crossed :(

@AnneTheAgile
Copy link
Author

@douglasknudsen @mezpahlan actually part of this proposed pull request did get undone in the referenced commit, right here;
359a492#diff-138ba9924fd1fadb6721753b08eded3bL772

Should I re-commit a tweak?
Will this be able to make it to the next release which maybe is next week?

@mezpahlan
Copy link

Hi @AnneTheAgile could you take a look at #53 . This is where I quickly reverted the change that knocked @douglasknudsen 's changes out. So as far as I am concerned the original mistake is now rectified in the master branch.

We released this as 1.3.2 feel free to update this PR to ensure that it doesn't re-revert the changes but I don't think that is necessary. I'll have a look at this PR now and then, yes, queue it up for a release.

Thanks for your support (and patience!).

@mezpahlan
Copy link

Ok I've applied the suggestions above and am just waiting on the checks.

@mezpahlan mezpahlan merged commit 3a0d807 into jenkinsci:master Oct 1, 2018
@AnneTheAgile
Copy link
Author

ty so much @mezpahlan !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants