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

Gulp task with argument containing the word "version" failing #6048

Closed
praga opened this issue Dec 15, 2017 · 7 comments

Comments

@praga
Copy link

@praga praga commented Dec 15, 2017

Environment

  • Server - VSTS

  • Agent - Hosted

    • Hosted VS2017

Issue Description

Gulp tasks with argument containing the term "version" don't seem to run at all. The same build with same source code and same arguments worked fine few days ago.

Error logs

This is the output with arguments
2017-12-15T05:26:33.0436184Z [command]C:\npm\prefix\gulp.cmd build --gulpfile d:\a\1\s\gulpfile.js --env stage --version 0.1.101
2017-12-15T05:26:49.2551701Z [05:26:49] CLI version 1.4.0
2017-12-15T05:26:49.2551701Z [05:26:49] Local version 3.9.1
2017-12-15T05:26:49.2952021Z ##[section]Finishing: gulp build staging app

@bryanmacfarlane

This comment has been minimized.

Copy link
Contributor

@bryanmacfarlane bryanmacfarlane commented Dec 16, 2017

Can't repro. Are you sure it isn't something specific to your gulfile.js file?

Can you include a small repro with a gulpfile.js included (doesn't have to be yours) with the task inputs that repros the behavior?

@praga

This comment has been minimized.

Copy link
Author

@praga praga commented Dec 16, 2017

I re-queued a successful build (a build from a different repo with no changes which ran fine few weeks ago) and that failed as well. I will double check my gulp file and arguments again and try to create a repo to reproduce this.

@praga praga changed the title Gulp task with arguments dont work Gulp task with argument containing the word "version" failing Dec 18, 2017
@praga

This comment has been minimized.

Copy link
Author

@praga praga commented Dec 18, 2017

@bryanmacfarlane I managed to replicate the issue. I initially thought it was to do with the arguments, however, after more investigation, it happens only if you have an environmental variable called "version". This used to work before, so I do not know what has changed.

@moswald

This comment has been minimized.

Copy link
Member

@moswald moswald commented Nov 15, 2018

@praga I'm going to close this issue as it is almost a year old and there has been no activity and a lot of changes have gone out to Azure DevOps. If this is still broken for you, please feel free to reopen the ticket. Thank you!

@moswald moswald closed this Nov 15, 2018
@michaelmaillot

This comment has been minimized.

Copy link

@michaelmaillot michaelmaillot commented May 23, 2019

Hi,

Sorry for digging up this post, but I just encountered the same problem, following both @FranckyC and @StfBauer articles on CI/CD of SPFx solutions.

I realized that hosting the build agent on "Hosted VS2017" make skip the gulp task "update-version" as you can see below:

image

But when switching to "Hosted" Agent, it works !

image

So, unlike @praga's problem, it's not because of an environment variable problem (but also strange anyway). Thanks to you anyway, because that's what gives me the clue 😉

@vivekayer

This comment has been minimized.

Copy link

@vivekayer vivekayer commented Jun 2, 2019

Hi,

Sorry for digging up this post, but I just encountered the same problem, following both @FranckyC and @StfBauer articles on CI/CD of SPFx solutions.

I realized that hosting the build agent on "Hosted VS2017" make skip the gulp task "update-version" as you can see below:

image

But when switching to "Hosted" Agent, it works !

image

So, unlike @praga's problem, it's not because of an environment variable problem (but also strange anyway). Thanks to you anyway, because that's what gives me the clue 😉

Is there a temporary workaround for this?

@michaelmaillot

This comment has been minimized.

Copy link

@michaelmaillot michaelmaillot commented Jun 3, 2019

Yes : switch the Agent to take another than "Hosted VS2017"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.