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

Ability to group several build definitions #12

Merged
merged 5 commits into from
Jun 28, 2017

Conversation

michelkaporin
Copy link
Contributor

As part of work on automating smoke tests for VS Code and creating build definitions to run them scheduled (see microsoft/vscode#28586 and microsoft/vscode#27845) I found your extension that provides capabilities we want to use in our dev work - such as seeing status of the builds in the status bar. I'd like to thank you for building it!

One missing piece was that you cannot group build definitions in a single status indicator. We have the following scenario which made me to do this PR:

  • We have build definition per each platform we run a smoke test on (Windows, Linux, OS X)
  • If any of the builds failed, we would like to see it in the status bar indicator.

Hence, I forked your extension and worked on some amends that required to enable grouped build. I also did little cosmetic changes in vstsbuildstatusbar.ts.

It would be great if you can merge those in, however if you feel that this functionality is out of scope for your extension, then I will publish a separate extension, mentioning that it is a fork of yours. Let me know what is more acceptable for you 🙂

Thank you.

@jlandersen jlandersen self-requested a review June 20, 2017 08:07
@jlandersen
Copy link
Owner

Hey, thanks for the PR! Will be happy to bring this feature into this extension. I will take a look at it asap.

@michelkaporin
Copy link
Contributor Author

@jlandersen when do you plan to look into it?

Just to let you know - another thing on my to-do list is to move authentication password out from settings (e.g. to OS native password storage). Not sure yet by which means to do it yet (proposing credentials API for VS Code or leveraging existing solutions as keytar). If too many code amends will be happening, I think creating a forked extension would make more reason for me.

@jlandersen
Copy link
Owner

Hi @michelkaporin

Apologies, I have been away for a few days - my plan was to look at it and hopefully get it merged + pushed on Wednesday (so just a couple of more days :-) ).

Re moving auth passwords out. It definitely makes sense. I was thinking of environment variables at one point, but if you have better suggestions I am open for merging it in as well!

@michelkaporin
Copy link
Contributor Author

michelkaporin commented Jun 27, 2017

@jlandersen Thanks, I will check back on Wednesday then.

Environment variables are not also very safe, but considered it also at one point. Thus, I've made a proposal for credentials API in VS Code with a potential to leverage it - microsoft/vscode#15414 (comment).
Currently we decided to postpone looking into password issue until we come up with a plan on that.

Copy link
Owner

@jlandersen jlandersen left a comment

Choose a reason for hiding this comment

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

Looks good - just posted a single request, other than that LGTM

if (!this.activeDefinition) {
this.statusBar.displayInformation("Select build definition", "");

if (!this.activeDefinitions) {
Copy link
Owner

Choose a reason for hiding this comment

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

You need to extend this condition to handle the initial case where activeDefinitions is an empty array. It is no longer null initially. As a result line 72 fails because it expects an item at position 0.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch! Sorted.

@jlandersen jlandersen merged commit f0b2759 into jlandersen:master Jun 28, 2017
@jlandersen
Copy link
Owner

Great, thanks a lot!

@jlandersen
Copy link
Owner

0.7.0 is live on the marketplace

@michelkaporin
Copy link
Contributor Author

Perfect, thank you @jlandersen !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants