Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make --latest the default
See original GitHub issue--latest only affects dependency resolution
It’s not great to request a plugin and to see it install 5 other dependencies and see that they now need updating, which leads to either having to specify every plugin, or learning about the --latest flag.
Proposal:
Changing the flag to take an argument:
--latest=true
--latest=false
And have it default to true
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Twitter No Longer Lets You See Latest Tweets by Default
In a controversial move that has drawn criticism from users, Twitter is no longer allowing users to see the latest tweets first by...
Read more >Change default programs in Windows
Select Start > Settings > Apps > Default apps. To change the default app, you can do either of the following: Set a...
Read more >Twitter rolls back update that removes chronological timeline
Twitter has decided to roll back the update that removed the option to access the timeline in chronological order by default.
Read more >Twitter's latest update makes its algorithmic timeline ...
Twitter's latest update makes its algorithmic timeline the default once again. March. 11.
Read more >Twitter Looks to Make it Easier to Access a Chronological ...
Twitter's testing a new option that will make it easier for users to switch across to a reverse-chronological timeline of tweets from the ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
So the behavior would change for users that don’t use
--latest.I added it to the 2.0 scope. Installing latest by default is how the existing Jenkins core logic operates, so I would follow the same behavior