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

Using with Jenkins, output says file is built but folder does not show the file #403

Closed
invinciblemuffi opened this issue May 13, 2016 · 9 comments

Comments

@invinciblemuffi
Copy link

Server: CentOS
Build Tool: Jenkins 2.x
Problem: Src and Destination path are the same, want to minify js files in src folder and should be updated in that same folder where that file is present.
The console output says, "Writing file include/abc.js", when checked in server file system, the file does not show as updated file. It still shows the original one.
If I change the destination path, then the minified files are written out properly.
Is this some kind of issue or expected behavior that the plugin cannot overwrite the src file which it is minifying and update it with the new minified one.

@avdg
Copy link
Contributor

avdg commented May 13, 2016

I saw some comments on a unmerged commit that might be a fix, however, there was no pr being made here and the way github is set up I'm not sure how to find that specific patch so I could link it anyway.

@invinciblemuffi
Copy link
Author

So you mean to say, it is an issue which is still not fixed and in open state

@avdg
Copy link
Contributor

avdg commented May 13, 2016

It's not even tracked on an issue tracker

@avdg
Copy link
Contributor

avdg commented May 13, 2016

So yeah, while at it, open the discussion :-)

@invinciblemuffi
Copy link
Author

Can you guide me how to find this issue, so that I can show it to my other team mates

@avdg
Copy link
Contributor

avdg commented May 13, 2016

Hmm.. I think the issue was about something else (there was some renaming happening). This question however is asked a lot I think but I need to use search engine and stack overflow myself :/.

@avdg
Copy link
Contributor

avdg commented May 13, 2016

If you can, it might be better to ask on stack overflow. Github is just for issues with the package itself or pull requests

@invinciblemuffi
Copy link
Author

ok will check

@alexlamsl
Copy link
Contributor

Setting destination same as source works in the latest version - closing.

Demonstrate with a (minimal) reproducible test case if you still have any issues.

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

No branches or pull requests

3 participants