-
Improvement
-
Resolution: Postponed
-
Major
-
-
Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2, Blue Ocean 1.1-beta4, Blue Ocean 1.1, Blue Ocean 1.1
Given the increasing tempo of build failures to to npm, the challenges with shrinkwrap and the inability to use mirrors, it may be time to evaluate the use of yarn as an alternative.
Approach
- General things to validate
- Ensure "run scripts" still work with yarn
- maven-frontend-plugin supports yarn natively, so we just need to switch this over.
- Do local installs work nicely? (for rapid development). Can we obviate or at least better integrate w/ slink so rapid dev is more seamless? Check out "yarn link"
- JDL Next
- Need to determine if/how a Yarn-published module is able to freeze its dependencies when pulled in via npm (since there is no shrink, probably not, but maybe there's some magic)
- Publish some beta JDL's and then pull them in via a blueocean-plugin PR to ensure ATH passes and things work, etc
- blueocean-core-js
- Do the same as above
- At this point perhaps we add JDL as a peerDep and avoid the need to republish core-js each time new JDL is published (large pain point)
- blueocean-web, dashboard and personalization
- Port these over to yarn as well
- Test with Artifactory
- is blocked by
-
JENKINS-44423 Upgrading blueocean to plugin-pom:2.8+ breaks unit tests
-
- Closed
-
- links to
[JENKINS-43411] Evaluate yarn
| Rank | New: Ranked higher |
| Description | Original: Given the increasing tempo of build failures to to npm, the challenges with shrinkwrap and the inability to use mirrors, it may be time to evaluate the use of yarn as an alternative. |
New:
Given the increasing tempo of build failures to to npm, the challenges with shrinkwrap and the inability to use mirrors, it may be time to evaluate the use of yarn as an alternative. Approach - General things to validate -- Ensure "run scripts" still work with yarn -- What's the best way to get yarn installed? I believe it can be installed via npm, but it would be nice if we could eliminate that dependency. Might require some extended work in maven-frontend-plugin. There was discussion about that when yarn was announced but the maintainer said it wasn't on his radar. Would it be worth implementing that and possibly contributing it back? -- Do local installs work nicely? (for rapid development). Can we obviate or at least better integrate w/ slink so rapid dev is more seamless? - JDL Next -- Can evaluate how easy Yarn is to use for standalone JS projects -- Need to determine if/how a Yarn-published module is able to freeze its dependencies when pulled in via npm (since there is no shrink, probably not, but maybe there's some magic) -- Publish some beta JDL's and then pull them in via a blueocean-plugin PR to ensure ATH passes and things work, etc - blueocean-core-js -- Do the same as above -- At this point perhaps we add JDL as a peerDep and avoid the need to republish core-js each time new JDL is published (large pain point) - blueocean-web, dashboard and personalization -- Port these over to yarn as well |
| Description |
Original:
Given the increasing tempo of build failures to to npm, the challenges with shrinkwrap and the inability to use mirrors, it may be time to evaluate the use of yarn as an alternative. Approach - General things to validate -- Ensure "run scripts" still work with yarn -- What's the best way to get yarn installed? I believe it can be installed via npm, but it would be nice if we could eliminate that dependency. Might require some extended work in maven-frontend-plugin. There was discussion about that when yarn was announced but the maintainer said it wasn't on his radar. Would it be worth implementing that and possibly contributing it back? -- Do local installs work nicely? (for rapid development). Can we obviate or at least better integrate w/ slink so rapid dev is more seamless? - JDL Next -- Can evaluate how easy Yarn is to use for standalone JS projects -- Need to determine if/how a Yarn-published module is able to freeze its dependencies when pulled in via npm (since there is no shrink, probably not, but maybe there's some magic) -- Publish some beta JDL's and then pull them in via a blueocean-plugin PR to ensure ATH passes and things work, etc - blueocean-core-js -- Do the same as above -- At this point perhaps we add JDL as a peerDep and avoid the need to republish core-js each time new JDL is published (large pain point) - blueocean-web, dashboard and personalization -- Port these over to yarn as well |
New:
Given the increasing tempo of build failures to to npm, the challenges with shrinkwrap and the inability to use mirrors, it may be time to evaluate the use of yarn as an alternative. Approach - General things to validate -- Ensure "run scripts" still work with yarn -- What's the best way to get yarn installed? I believe it can be installed via npm, but it would be nice if we could eliminate that dependency. Might require some extended work in maven-frontend-plugin. There was discussion about that when yarn was announced but the maintainer said it wasn't on his radar. Would it be worth implementing that and possibly contributing it back? -- Do local installs work nicely? (for rapid development). Can we obviate or at least better integrate w/ slink so rapid dev is more seamless? - JDL Next -- Need to determine if/how a Yarn-published module is able to freeze its dependencies when pulled in via npm (since there is no shrink, probably not, but maybe there's some magic) -- Publish some beta JDL's and then pull them in via a blueocean-plugin PR to ensure ATH passes and things work, etc - blueocean-core-js -- Do the same as above -- At this point perhaps we add JDL as a peerDep and avoid the need to republish core-js each time new JDL is published (large pain point) - blueocean-web, dashboard and personalization -- Port these over to yarn as well |
| Description |
Original:
Given the increasing tempo of build failures to to npm, the challenges with shrinkwrap and the inability to use mirrors, it may be time to evaluate the use of yarn as an alternative. Approach - General things to validate -- Ensure "run scripts" still work with yarn -- What's the best way to get yarn installed? I believe it can be installed via npm, but it would be nice if we could eliminate that dependency. Might require some extended work in maven-frontend-plugin. There was discussion about that when yarn was announced but the maintainer said it wasn't on his radar. Would it be worth implementing that and possibly contributing it back? -- Do local installs work nicely? (for rapid development). Can we obviate or at least better integrate w/ slink so rapid dev is more seamless? - JDL Next -- Need to determine if/how a Yarn-published module is able to freeze its dependencies when pulled in via npm (since there is no shrink, probably not, but maybe there's some magic) -- Publish some beta JDL's and then pull them in via a blueocean-plugin PR to ensure ATH passes and things work, etc - blueocean-core-js -- Do the same as above -- At this point perhaps we add JDL as a peerDep and avoid the need to republish core-js each time new JDL is published (large pain point) - blueocean-web, dashboard and personalization -- Port these over to yarn as well |
New:
Given the increasing tempo of build failures to to npm, the challenges with shrinkwrap and the inability to use mirrors, it may be time to evaluate the use of yarn as an alternative. Approach - General things to validate -- Ensure "run scripts" still work with yarn -- What's the best way to get yarn installed? I believe it can be installed via npm, but it would be nice if we could eliminate that dependency. Might require some extended work in maven-frontend-plugin. There was discussion about that when yarn was announced but the maintainer said it wasn't on his radar. Would it be worth implementing that and possibly contributing it back? -- Do local installs work nicely? (for rapid development). Can we obviate or at least better integrate w/ slink so rapid dev is more seamless? Check out "yarn link" - JDL Next -- Need to determine if/how a Yarn-published module is able to freeze its dependencies when pulled in via npm (since there is no shrink, probably not, but maybe there's some magic) -- Publish some beta JDL's and then pull them in via a blueocean-plugin PR to ensure ATH passes and things work, etc - blueocean-core-js -- Do the same as above -- At this point perhaps we add JDL as a peerDep and avoid the need to republish core-js each time new JDL is published (large pain point) - blueocean-web, dashboard and personalization -- Port these over to yarn as well |
| Assignee | New: Cliff Meyers [ cliffmeyers ] |
| Epic Link | New: JENKINS-35749 [ 171790 ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Description |
Original:
Given the increasing tempo of build failures to to npm, the challenges with shrinkwrap and the inability to use mirrors, it may be time to evaluate the use of yarn as an alternative. Approach - General things to validate -- Ensure "run scripts" still work with yarn -- What's the best way to get yarn installed? I believe it can be installed via npm, but it would be nice if we could eliminate that dependency. Might require some extended work in maven-frontend-plugin. There was discussion about that when yarn was announced but the maintainer said it wasn't on his radar. Would it be worth implementing that and possibly contributing it back? -- Do local installs work nicely? (for rapid development). Can we obviate or at least better integrate w/ slink so rapid dev is more seamless? Check out "yarn link" - JDL Next -- Need to determine if/how a Yarn-published module is able to freeze its dependencies when pulled in via npm (since there is no shrink, probably not, but maybe there's some magic) -- Publish some beta JDL's and then pull them in via a blueocean-plugin PR to ensure ATH passes and things work, etc - blueocean-core-js -- Do the same as above -- At this point perhaps we add JDL as a peerDep and avoid the need to republish core-js each time new JDL is published (large pain point) - blueocean-web, dashboard and personalization -- Port these over to yarn as well |
New:
Given the increasing tempo of build failures to to npm, the challenges with shrinkwrap and the inability to use mirrors, it may be time to evaluate the use of yarn as an alternative. Approach - General things to validate -- Ensure "run scripts" still work with yarn -- maven-frontend-plugin supports yarn natively, so we just need to switch this over. -- Do local installs work nicely? (for rapid development). Can we obviate or at least better integrate w/ slink so rapid dev is more seamless? Check out "yarn link" - JDL Next -- Need to determine if/how a Yarn-published module is able to freeze its dependencies when pulled in via npm (since there is no shrink, probably not, but maybe there's some magic) -- Publish some beta JDL's and then pull them in via a blueocean-plugin PR to ensure ATH passes and things work, etc - blueocean-core-js -- Do the same as above -- At this point perhaps we add JDL as a peerDep and avoid the need to republish core-js each time new JDL is published (large pain point) - blueocean-web, dashboard and personalization -- Port these over to yarn as well |
| Description |
Original:
Given the increasing tempo of build failures to to npm, the challenges with shrinkwrap and the inability to use mirrors, it may be time to evaluate the use of yarn as an alternative. Approach - General things to validate -- Ensure "run scripts" still work with yarn -- maven-frontend-plugin supports yarn natively, so we just need to switch this over. -- Do local installs work nicely? (for rapid development). Can we obviate or at least better integrate w/ slink so rapid dev is more seamless? Check out "yarn link" - JDL Next -- Need to determine if/how a Yarn-published module is able to freeze its dependencies when pulled in via npm (since there is no shrink, probably not, but maybe there's some magic) -- Publish some beta JDL's and then pull them in via a blueocean-plugin PR to ensure ATH passes and things work, etc - blueocean-core-js -- Do the same as above -- At this point perhaps we add JDL as a peerDep and avoid the need to republish core-js each time new JDL is published (large pain point) - blueocean-web, dashboard and personalization -- Port these over to yarn as well |
New:
Given the increasing tempo of build failures to to npm, the challenges with shrinkwrap and the inability to use mirrors, it may be time to evaluate the use of yarn as an alternative. Approach - General things to validate -- Ensure "run scripts" still work with yarn -- maven-frontend-plugin supports yarn natively, so we just need to switch this over. -- Do local installs work nicely? (for rapid development). Can we obviate or at least better integrate w/ slink so rapid dev is more seamless? Check out "yarn link" - JDL Next -- Need to determine if/how a Yarn-published module is able to freeze its dependencies when pulled in via npm (since there is no shrink, probably not, but maybe there's some magic) -- Publish some beta JDL's and then pull them in via a blueocean-plugin PR to ensure ATH passes and things work, etc - blueocean-core-js -- Do the same as above -- At this point perhaps we add JDL as a peerDep and avoid the need to republish core-js each time new JDL is published (large pain point) - blueocean-web, dashboard and personalization -- Port these over to yarn as well - Test with Artifactory |
| Link | New: This issue relates to INFRA-1139 [ INFRA-1139 ] |