Skip to content

Conversation

@TravisEz13
Copy link
Member

Currently, every merge is also publishing.

@TravisEz13 TravisEz13 added the Area-Maintainers-Build specific to affecting the build label Aug 7, 2017
Copy link
Member

@adityapatwardhan adityapatwardhan left a comment

Choose a reason for hiding this comment

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

I found another issue, we seem to be updating the badge on full build, including the one with [Feature]. We need a way to identify a CRON build and then do nuget publish and badge update.

tools/travis.ps1 Outdated
Copy link
Member

Choose a reason for hiding this comment

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

Typo in allready -> already

tools/travis.ps1 Outdated
Copy link
Member

Choose a reason for hiding this comment

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

This also published if it is [Feature] run?

Copy link
Member Author

Choose a reason for hiding this comment

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

Only if we merge a feature... that is equivalent to a daily build, I'm fine with it. If it's a PR, it won't publish. And if you squash merge, you will likely, remove the [Feature] from the commit message.

Copy link
Member Author

Choose a reason for hiding this comment

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

actually, a true merge would change the description of the last commit message too. Only merging to master using the rebase option would have this possible effect.

@TravisEz13
Copy link
Member Author

The badge issue is being fixed in #4536

tools/travis.ps1 Outdated
Copy link
Member

Choose a reason for hiding this comment

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

After merging a PR to master, if the commit message happen to have [Feature] tag, we will publish the nuget package as well. Is that desired? Maybe we should use $isDailyBuild instead.

Copy link
Member Author

Choose a reason for hiding this comment

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

Rebased, and updated.

@TravisEz13 TravisEz13 force-pushed the OnlyPushToNugetOnFullBuilds branch from 8afb947 to b4bcbf1 Compare August 9, 2017 22:44
Copy link
Member

@adityapatwardhan adityapatwardhan left a comment

Choose a reason for hiding this comment

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

LGTM

@TravisEz13 TravisEz13 merged commit b3ebdaf into PowerShell:master Aug 11, 2017
@TravisEz13 TravisEz13 deleted the OnlyPushToNugetOnFullBuilds branch August 11, 2017 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Maintainers-Build specific to affecting the build

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants