1227926 - Auto-sync doesn't work between fbug SVN and getfirebug.com

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Jan Honza Odvarko [:Honza] (always need-info? me)]

getfirebug.com used to auto update from SVN repository.

SVN:
https://svn.mozilla.org/projects/getfirebug.com/

URL:
getfirebug.com/releases

But it doesn't work anymore (for about a week for now)

Honza

Comment 1

[C. Liang [:cyliang]]

It looks like there are issues with some of the svn:externals entries that's causing errors. [1]  Did the svn externals definitions get tweaked?


[1]

Fetching external item into 'tests/head':
Skipped 'tests/head/firebug.html' -- An obstructing working copy was found
Skipped 'tests/head/known-failures.html' -- An obstructing working copy was found
Skipped 'tests/head/test-bot.html' -- An obstructing working copy was found
External at revision 25063.


Fetching external item into 'tests/1.9':
Skipped 'tests/1.9/.htaccess' -- An obstructing working copy was found
Skipped 'tests/1.9/firebug.html' -- An obstructing working copy was found
svn: warning: W200004: Could not convert '' into a number


Fetching external item into 'tests/1.10':
Skipped 'tests/1.10/firebug.html' -- An obstructing working copy was found
svn: warning: W200004: Could not convert '' into a number


Fetching external item into 'tests/1.11':
Skipped 'tests/1.11/firebug.html' -- An obstructing working copy was found
Skipped 'tests/1.11/known-failures.html' -- An obstructing working copy was found
Skipped 'tests/1.11/test-bot.html' -- An obstructing working copy was found
External at revision 25063.


Fetching external item into 'tests/1.12':
Skipped 'tests/1.12/firebug.html' -- An obstructing working copy was found
Skipped 'tests/1.12/known-failures.html' -- An obstructing working copy was found
Skipped 'tests/1.12/test-bot.html' -- An obstructing working copy was found
External at revision 25063.

Comment 2

[Jan Honza Odvarko [:Honza] (always need-info? me)]

(In reply to C. Liang [:cyliang] from comment #1)
> It looks like there are issues with some of the svn:externals entries that's
> causing errors. [1]  Did the svn externals definitions get tweaked?
No, I don't know about any changes.

Honza

Comment 3

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Are there any progress on this? It's really blocking our Firebug releases.
If it helps we can remove svn:externals entries you've listed in comment #1

Honza

Comment 4

[C. Liang [:cyliang]]

If there is no reason to retain the svn externals, I would suggest removing them.

I *think* the update process should work now but without understanding why the conflict between the svn external definitions and the local directory exist, I don't know if this situation will re-occur.

Steps taken:
   * Temporarily moved tests directory to another location.
   * Forced an 'svn cleanup'.
   * Re-updated test ('svn update tests')
   * Forced run of the update script (usually executed by cron).

Comment 5

[C. Liang [:cyliang]]

The update process looks like it is broken again so, if the svn externals can be safely removed, please do so.  [1]  

'svn cleanup' by itself does not fix the issue.  I suspect that I'll need to repeat what I did in comment #4 but it appears that it only works once before it gets into a broken state again. =\



[1]  svn: warning: W155004: Working copy '/data/genericrhel6/src/getfirebug.com/getfirebug/tests/head' locked.
svn: warning: W155004: Working copy '/data/genericrhel6/src/getfirebug.com/getfirebug/tests/1.11' locked.
svn: E205011: Failure occurred processing one or more externals definitions

Comment 6

[Jan Honza Odvarko [:Honza] (always need-info? me)]

svn:externals on `getfirebug.com/tags/production/tests`

https://github.com/firebug/test-result-viewer/trunk result-viewer
https://github.com/firebug/manual-tests/trunk manual
https://github.com/firebug/firebug/trunk/tests/content head
https://github.com/firebug/firebug/branches/firebug1.9/tests/content 1.9
https://github.com/firebug/firebug/branches/firebug1.10/tests/content 1.10
https://github.com/firebug/firebug/branches/firebug1.11/tests/content 1.11
https://github.com/firebug/firebug/branches/firebug1.12/tests/content 1.12
https://github.com/firebug/firebug/trunk/tests/templates templates

svn:externals on `getfirebug.com/tags/production`
https://github.com/firebug/swarms/

svn:externals on `getfirebug.com/tags/production-1.4`
tests http://fbug.googlecode.com/svn/tests

svn:externals on `getfirebug.com/tags/production-1.5`
tests http://fbug.googlecode.com/svn/tests

svn:externals on `getfirebug.com/tags/production-1.5.1`
tests http://fbug.googlecode.com/svn/tests

svn:externals on `getfirebug.com/tags/trunk`
tests http://fbug.googlecode.com/svn/tests

---

All should be removed at revision 149967

Honza

Comment 7

[C. Liang [:cyliang]]

Honza: I've found one last set of SVN conflicts between what's on the server and what's in the repo.  I'd like to know if it's safe to remove the local conflict.

Locally, it looks like there is an svn external defined pointing to swarms:

  $ svn propget svn:externals
  swarms.github https://github.com/firebug/swarms/

There is a symlink inside the releases directory that ends up pointing to the swarms.github contents.

It doesn't look like this external is listed in the repo.  Is swarms still needed?

Comment 8

[Jan Honza Odvarko [:Honza] (always need-info? me)]

(In reply to C. Liang [:cyliang] from comment #7)
> Is swarms still needed?
No, it can be removed.

Honza

Comment 9

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Just adding NI so, this isn't forgotten.
Honza

Comment 10

[C. Liang [:cyliang]]

I believe the local SVN repository is fixed and auto-updates should be working.

I ran the auto-update script manually several times without any issue.  The last automated run of the script updated completed successfully:

   > finished at Thu Jan  7 14:15:04 PST 2016

I don't know if you want to make a change to the repo and see it reflected on-line as verification or not.

Comment 11

[Jan Honza Odvarko [:Honza] (always need-info? me)]

The site is now updated, thanks!

(I'll ping you in case further changes are not propagated).

Honza