I'm running BuildMaster version 4.8.6 and I'd like to delete old build artifacts.
This question (on the BuildMaster's maker's Q&A section of their site) – Release/Build History – mentions that, besides a trigger in a beta extension and a 'release archiving' feature that may or may not have been implemented, old artifacts "need to be deleted manually".
How do I delete an artifact manually? Is there anything to it other than just deleting the relevant files and directories under the BuildMaster\Artifacts\ directory?
I asked this same question on the BuildMaster's maker's Q&A section of their site:
How to (manually) delete old artifacts? | Support Q & A | Inedo
Based on the answer on the question there, here are steps to manually delete a single artifact:
From a (any) BuildMaster page, go to the Settings & Administration page.
In the "System Settings" group, click "Administrative Edits".
In the "Artifacts" group, click "Purge Artifact".
In the "Purge Build Artifact" popup, pick the relevant "Application", "Release", "Build", and "Artifact".
Click the "Purge Build Artifact" button.
Related
SUMMARY
I created an app App using Xamarin Form and Visual Studio 2019.
Folder/file structure:
[d] App
|-[d] App
| |-[d] App
| | |- ...
| |-[d] App.Android
| | |- ...
| |-[d] App.iOS
| |- ...
|-[f] App.sln
I finally got rid of all the errors and warnings and tried to upload APK to Google Play Console. I found multiple *.apk files and googled that I have to upload the one that has "-Signed" in its name. It resides in App/App/App.Android/bin/Debug. Upon the failed upload I got the following message:
Upload failed
You uploaded a debuggable APK or Android App Bundle. For security reasons you need to disable debugging before it can be published in Google Play. Find out more about debuggable APKs or Android App Bundles.
You uploaded an APK or Android App Bundle that was signed in debug mode. You need to sign your APK or Android App Bundle in release mode. Find out more about signing.
WHAT I DID
I found one SO Q&A that says I should change my project from Debug mode to Release.
I found that, if I right-click App.Android in (VS) Solution Explorer and choose Properties, I can choose Android Options tab on the left and then "Configuration: Release". It didn't work. But there is also Android Package Signing tab on the left which has the "Sign the .APK file using the following keystore details" checkbox unchecked.
Before I delved into the latter, I also found that in Visual Studio top-most menu I can open "Build" and choose "Configuration Manager" where I can change "Active solution configuration" to "Release" which in change turn all three project to "Release". I did so and it still didn't work. (No new *.apk file was created)
In the last link in quoted message above I found instructions on how to create the key needed
In the menu bar, click Build > Build > Generate Signed Bundle/APK.
In the Generate Signed Bundle or APK dialog, select Android App Bundle or APK and click Next.
Below the field for Key store path, click Create new.
{so forth...}
but these are only for Android Studio not Visual Studio. Is there any way how to do it with Visual Studio?
Xamarin can be annoying for newer users, especially if you have made any changes to the defaults unknowingly. And the release configuration in the default template creates a debuggable APK, so that's not helpful either.
Let's follow the steps to publish an app, and disable debugging from the Release APK:
Make sure you choose Android, Release configuration in the main window as shown.
Then double click on the Android project to open the Project Options and navigate to Compiler. Make sure that for the "Release" Configuration selected, you change the Debug Information to "None". Don't forget to press OK and save the changes.
Rebuild All.
Right click on the Android project and select Archive for Publishing.
Once archived, continue to Sign and Distribute as you were doing earlier.
Make sure to read the comments for more details!
Using WebStorm 11.0.3 to build a Meteor app. I noticed that it takes too long to come up with some context sensitive menus with the busy colourful circle revolving.
I tried to right click on the project to see if there is "ignore folder" but did not find it.
What un necessary folders to exclude and how in order to speed up indexing on the hope that it will be faster IDE? Thanks
You can definitely exclude the .meteor/local folder. It will make indexing way more faster than what you are experiencing now.
First go to,
File -> settings -> Language & Frameworks -> JavaScript -> Meteor
make sure the "Automatically exclude '.meteor/local' directory on open project" is selected.
click OK.
Then from the project tree tool bar settings menu, untick "Show Excluded Files"
Build for debug is just press on the PLAY symbol, but I don't know how to Build for distribution/release?
The short answer is:
choose the iOS scheme from the
drop-down near the run button from
the menu bar
choose product > archive in the
window that pops-up
click 'validate'
upon successful validation, click
'submit'
You can use command line tool to build the release version. Next to your project folder, i.e.
$ ls
...
Foo.xcodeproj
...
Type the following build command:
$ xcodebuild -configuration Release
The "play" button is specifically for build and run (or test or profile, etc). The Archive action is intended to build for release and to generate an archive that is suitable for submission to the app store. If you want to skip that, you can choose Product > Build For > Archive to force the release build without actually archiving. To find the built product, expand the Products group in the Project navigator, right-click the product and choose to show in Finder.
That said, you can click and hold the play button for a menu of other build actions (including Build and Archive).
XCode>Product>Schemes>Edit Schemes>Run>Build Configuration
They've bundled all the target/build configuration/debugging options stuff into "schemes". The transition guide has a good explanation.
I have a large app that was having problems uploading to the AppStore using the archive method you will find in XCode 4. The activity indicator kept spinning for hours whether I was trying to validate or distribute, so I created a support ticket to Apple. During that process, I found out you could right click on the .app in your Products folder inside the Project Navigator of XCode, and compress the app to submit using the Application Loader 2.5.1. (aka the old method). Only the Debug - iphoneos folder is accessible this way (for now) and once Apple responded, this is what they had to say:
I'm glad to hear that Application Loader has provided you a viable workaround. Discussing this situation internally, we're not sure that submitting the Debug build will pose too much of a problem (so long as it was signed with the App Store distribution profile, as you mentioned it was). The app will likely be slower as the debug switches are turned on and optimizations are turned off for the Debug configuration, though it will still run. App Review will ultimately determine whether or not that's ok, as I'm not sure that's something they check for. You could try reaching out directly to App Review to confirm this, if you wish. However, since App Loader is working for you, I do recommend rebuilding the app with your Release configuration and resubmitting to play it safe. To find your Release build in Xcode 4.x, control-click on the Application Archive on the Archives tab in the organizer, and choose "Show in Finder." Then, control-click on the .xcarchive file in Finder and choose "Show Package Contents." The release built .app file should be located within the /Products/Applications folder.
This was very helpful information for developers who are having problems with the archive method, and my app is now uploading successfully without any concern that it won't run to the best of it's ability.
To set the build configuration to Debug or Release, choose 'Edit Scheme' from the 'Product' menu.
Then you see a clear choice.
The Apple Transition Guide mentions a button at the top left of the Xcode screen, but I cannot see it in Xcode 4.3.
That part is now located under Schemes. If you edit your schemes you will see that you can set the debug/release/adhoc/distribution build config for each scheme.
Product -> Archive, later, press the distribute button and check the option Export as Application or what you want
Build for debug is just press on the PLAY symbol, but I don't know how to Build for distribution/release?
The short answer is:
choose the iOS scheme from the
drop-down near the run button from
the menu bar
choose product > archive in the
window that pops-up
click 'validate'
upon successful validation, click
'submit'
You can use command line tool to build the release version. Next to your project folder, i.e.
$ ls
...
Foo.xcodeproj
...
Type the following build command:
$ xcodebuild -configuration Release
The "play" button is specifically for build and run (or test or profile, etc). The Archive action is intended to build for release and to generate an archive that is suitable for submission to the app store. If you want to skip that, you can choose Product > Build For > Archive to force the release build without actually archiving. To find the built product, expand the Products group in the Project navigator, right-click the product and choose to show in Finder.
That said, you can click and hold the play button for a menu of other build actions (including Build and Archive).
XCode>Product>Schemes>Edit Schemes>Run>Build Configuration
They've bundled all the target/build configuration/debugging options stuff into "schemes". The transition guide has a good explanation.
I have a large app that was having problems uploading to the AppStore using the archive method you will find in XCode 4. The activity indicator kept spinning for hours whether I was trying to validate or distribute, so I created a support ticket to Apple. During that process, I found out you could right click on the .app in your Products folder inside the Project Navigator of XCode, and compress the app to submit using the Application Loader 2.5.1. (aka the old method). Only the Debug - iphoneos folder is accessible this way (for now) and once Apple responded, this is what they had to say:
I'm glad to hear that Application Loader has provided you a viable workaround. Discussing this situation internally, we're not sure that submitting the Debug build will pose too much of a problem (so long as it was signed with the App Store distribution profile, as you mentioned it was). The app will likely be slower as the debug switches are turned on and optimizations are turned off for the Debug configuration, though it will still run. App Review will ultimately determine whether or not that's ok, as I'm not sure that's something they check for. You could try reaching out directly to App Review to confirm this, if you wish. However, since App Loader is working for you, I do recommend rebuilding the app with your Release configuration and resubmitting to play it safe. To find your Release build in Xcode 4.x, control-click on the Application Archive on the Archives tab in the organizer, and choose "Show in Finder." Then, control-click on the .xcarchive file in Finder and choose "Show Package Contents." The release built .app file should be located within the /Products/Applications folder.
This was very helpful information for developers who are having problems with the archive method, and my app is now uploading successfully without any concern that it won't run to the best of it's ability.
To set the build configuration to Debug or Release, choose 'Edit Scheme' from the 'Product' menu.
Then you see a clear choice.
The Apple Transition Guide mentions a button at the top left of the Xcode screen, but I cannot see it in Xcode 4.3.
That part is now located under Schemes. If you edit your schemes you will see that you can set the debug/release/adhoc/distribution build config for each scheme.
Product -> Archive, later, press the distribute button and check the option Export as Application or what you want
I am getting an error in subclipse installation in flexs builder 3 professional
"No Features found on the selected site. Choose a different site or site category."
In past also, I have successfully installed sunclipse on FB3 taking help from links like 'http://markstar.co.uk/blog/2009/flashplatform/installing-and-using-subclipse-for-flex-builder-3/' and 'http://subclipse.tigris.org/servlets/ProjectProcess?pageID=p4wYuA'.
This time however I am facing some issues. I have taken following steps
(1)Help > Software updates > Find and install > new feature install > New Archive site.
(2) Then I have browsed it to the place where I have kept the downloaded zip 'site 1.0.6'.
(3) This was reflected in the list as 'site-1.0.6'
(4) As I clicked 'Finished' an error is popping up:
"No Features found on the selected site. Choose a different site or site category."
What could be the reason for this, any idea ?
Please help.
Thanks in advance.
Look like you are trying to use a subclipse plugin for an older version of Flex Builder. Flex Builder 3 is based on Eclipse 3.3 and you will have to use the 1.6 or the 1.4 series. Also, the "bare" zip file is usually not designed to be installed with "Software Updates".
An easy way to install Subclipse on FB 3 is:
Help -> Software Updates -> Find and install...
Click "Search for new features to install" then click Next
Add the following remote sites:
Name: (whatever you like, I used "Subclipse")
URL: http://subclipse.tigris.org/update_1.6.x
Name: Mylyn
URL: http://archive.eclipse.org/mylyn/drops/3.2.3/v20100217-0100/e3.3
Check "Mylyn", "Subclipse" and "Europa Discovery Site" then click "Finish"
Check the whole "Subclipse" tree
From the "Mylyn" tree select everything except "Java Development" and "Plug-in development"
From the "Europa Discovery Site" group open the "Graphical Editor and Frameworks" tree and select "Graphical Editing Framework"
If you don't need Mylyn integration don't add the remote Mylyn site and uncheck "Subclipse Integration for Mylyn 3" from the "Subclipse" subtree.
If you don't need the revision graph tool don't enable "Europa Discovery Site" and uncheck "Subversion revision graph" from the "Subclipse" subtree.
The downloaded zip is designed to be extracted into the Eclipse plugins directory, not to be used with the built-in update mechanism.
In the install updates dialog, add a new remote site with name "Subclipse" and URL http://subclipse.tigris.org/update_1.6.x. Install everything with "(Required)" in the name.
Thanks Lorenzo and Andrew for your support.
I have got the solution to this problem. Actually, the 'subclipse' was already installed for that Flex builder but I wasn't aware of. So whenever I was trying to add 'new local site' or 'new archive site' it was displaying an error. Actually, the message should have been that the feature is already installed but it was displaying 'No Features found on the selected site. Choose a different site or site category'.
Thanks again for your help.
Also, as I am working behind a proxy, direct upgradation using URL doesn't work for me and hence I downlaod the zip and then add it.