Comments (12)
Because the last updated timestamp isn't shown in the output, it's not readily apparent in the table view why it's ordered this way.
What about ordering by build start time (descending)?
from acr.
Proposal: order by status then by build id desc
from acr.
Builds returned by the service are ordered by the timestamp (aka, build id) when they are triggered. To me a stable ordering makes more sense as a few implementations (e.g., show logs of the last updated build) would be tricky and confusing otherwise.
Client, if interested in a certain value of a certain column, can apply either a server side filter by specifying, for example, --name MyBuildTask
and/or --build-status Succeeded
, or a client side querying by specifying --query
.
from acr.
@djyou there's definitely a bug in the above because it doesn't do what you're saying. It's not being sorted by timestamp, aa7
and aa8
are out of order. Unless that's from an old CLI. Anyways, I still think it makes sense for all of the list builds commands to filter by status and then by time. It's a much more natural way to see things that are in progress than just time, since there's going to be a huge variance in build completion times. Imagine the mess it'd look like if you had Windows builds and Linux builds at the same time. Huge difference in start/stop times.
The current show logs
behavior is only useful for tiny pipelines with no builds in parallel. It shouldn't be a major feature that anyone depends on, so just showing the latest timestamp will get it correct 99.99% of the time.
from acr.
@ehotinger They are ordered by record's last updated timestamp. The above example means aa7
has an update later than that of aa8
.
The problem with ordering by status is that, given we have 8 statuses, if I have many Succeeded
and Failed
but a few builds in other statues. How will you order them meaningfully? Always show the many Succeeded
(or Failed
) builds before showing everything else, even if they are old and may overwhelm more recent builds? I don't see a simple solution here without introducing complex ordering (e.g., order by day, then status, then timestamp, etc.).
The fact that we support both server and client side filtering already provides enough flexibility and any additional (implicit) ordering done by us would be confusing IMO.
from acr.
lastUpdatedTime
is available in json, but as agreed, it's not shown in table. We can add it if needed, but I do agree with you ordering by build start time might make more sense here. We can tweak the message of show logs
to be the last started build. /cc @SteveLas
from acr.
A potential drawback to start-time-descending format would be that a long-running build could get pushed further down the list, and eventually get hidden by the later N builds (and stay there, even after it completes). With the last-updated ordering, it'd pop to the top when it completes.
from acr.
Sorry for the spam--one other option: order by duration, then last updated. This would pop currently running builds to the top (since duration is null), but preserve the current last updated sort for all other builds, regardless of status.
from acr.
I think we all agree we'll need the ability to filter and change ordering. The question seems to be, what should the default be.
@ehotinger brings up a good point, when we start mixing long running builds (assumed to be .NET FX and WindowsServerCore, but could be Java or who knows what), with quick running builds, perhaps spall test containers.
After running lots of builds over the weekend (I'm up to aa64), the initial build/queue time seems the most normal. But, I'm also looking at a watch -n1 az acr build-task list-builds
output. Meaning, the top is at the top of my screen. If I listed builds, and 50 scrolled by, it would be harder.
When do we get the default of 15 data rows?
Suggest we leave as build/queue time for now, and see what happens as we get more diverse builds and feedback.
from acr.
@SteveLas It's been merged and will be released soon by CLI team. You can run the docker image https://github.com/Azure/azure-cli#docker or install Edge release https://github.com/Azure/azure-cli#edge-builds for now.
from acr.
@djyou, can we tweak this a bit to show ordering based on initial queue date? When using watch, the ordering bounces and it's a bit confusing to track.
from acr.
This has been fixed from the server side, now list builds are ordered by their createTime
.
from acr.
Related Issues (20)
- Pull Through Caching from Another Azure Container Registry HOT 2
- Add support of registry.k8s.io type in cache rules HOT 1
- Rest api for get tags doesn respect n parameter (pagesize) HOT 2
- Scope Security/ Vulnerability scan to certain image tags only
- Catalog API only works with scope map * HOT 2
- Allow configuration of CORS headers for API access from web clients HOT 1
- Use Entra security principals with scope maps HOT 3
- ACR Cache error: too many requests to source registry for cache rule HOT 44
- connectivity_challenge_error grcsharedacr
- Unable to login into azure acr HOT 2
- Unable to login to container registry shazdevops HOT 1
- Auth Endpoint seems to require account parameter which is not part of the API Spec
- Cache elastic images HOT 1
- ACR Build with public access disabled HOT 1
- ACR streaming: failed to open remote file as tar file error HOT 6
- Cached images do not update. HOT 6
- Cannot create cache rule for public docker image `python:3.11-bookworm` due to naming rules HOT 3
- Cache zalando images
- Quay self-hosted Registry Caching
- token support for signed images HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from acr.