Re: Build failed in Jenkins: Allura #1353

These failures have been mostly related to disk space issues, so I've set the job to run on different jenkins hosts and tried again. Also notified bui...@apache.org about the issue to try to get it figured out. And one failure is due to https://forge-allura.apache.org/p/allura/tickets/8222/ bug

Jenkins build is back to normal : Allura #1354

See

Build failed in Jenkins: Allura #1350

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H30 (ubuntu xenial) in workspace > git rev-parse

[allura:tickets] #8225 Component delete everything end up with 404

- **status**: open --> closed - **assigned_to**: Shalitha Suranga - **Reviewer**: Dave Brondsema --- ** [tickets:#8225] Component delete everything end up with 404** **Status:** closed **Milestone:** unreleased **Created:** Tue Sep 04, 2018 05:57 PM UTC by Shalitha Suranga **Last Updated:**

Build failed in Jenkins: Allura #1352

See -- Started by user brondsem [EnvInject] - Loading node environment variables. Building remotely on H30 (ubuntu xenial) in workspace > git rev-parse

Build failed in Jenkins: Allura #1351

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H32 (ubuntu xenial) in workspace > git rev-parse

Build failed in Jenkins: Allura #1353

See Changes: [dbrondsema] [#8225] Redirect if current object is deleted [dbrondsema] [#8225] Skip 404 for non root and only when deleted [dbrondsema] [#8225] Fix skip 404 by validatiing request.referer

Re: Regarding forgeGit local problem

On 10/4/18 7:10 AM, Shalitha Suranga wrote: > Hi.. > > I tried to create Git repo for test project locally to work on some Git > related tickets > > But it hangs on "Repo status: initializing..." and got this error message > > Traceback (most recent call last): > File >

[allura:tickets] #8230 Make checklists interactive

Cool. Good job adding the things like activity entry, I had forgotten about that but that is good. I think it'd be a little better to not let people even check the boxes if they don't have permission. For example add a has_access check in "block wiki_extra_js" and don't do the JS if they

[allura:tickets] #8230 Make checklists interactive

Thank you. I will make some commits for the things as you explained above. And once we agree with general approach we will add for other non-repeacting things. For threads we will discuss an approach when we complete works for all of non-repeating things --- ** [tickets:#8230] Make

[allura:tickets] #8230 Make checklists interactive

Hi.. Dave Thank you for the guidance above content was really helped. I have made changes as per below - Added edit permission check if user has no permission displayed a notification saying "Changes will not persist" - Added activity entry as "modified wiki page" - Tested and no more

Regarding forgeGit local problem

Hi.. I tried to create Git repo for test project locally to work on some Git related tickets But it hangs on "Repo status: initializing..." and got this error message Traceback (most recent call last): File